Generalized EC Type 2 support EC Type 1&2 supporting bridges - PowerPoint PPT Presentation

bill
generalized ec type 2 support ec type 1 2 supporting bridges n.
Skip this Video
Loading SlideShow in 5 Seconds..
Generalized EC Type 2 support EC Type 1&2 supporting bridges PowerPoint Presentation
Download Presentation
Generalized EC Type 2 support EC Type 1&2 supporting bridges

play fullscreen
1 / 23
Download Presentation
Generalized EC Type 2 support EC Type 1&2 supporting bridges
92 Views
Download Presentation

Generalized EC Type 2 support EC Type 1&2 supporting bridges

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Generalized EC Type 2 supportEC Type 1&2 supporting bridges Maarten Vissers 2011-07-19

  2. Introduction • http://www.ieee802.org/1/files/public/docs2011/new-vissers-pbb-pbbte-eotn-common-network-arch-0511-v01.pptx presented common network architectures for PBB, PBB-TE and EOTN networks to determine the Tagging method of EC Type 2 signals in an EOTN • The last two slides in the above presentation indentified implications of the Tagging methods within PB, PBB I and PBB-TE networks • These slides were not addressed in Santa Fe meeting due to time constraints • This new presentation addresses the implications of the choice of I+S-Tagging of EC Type 2 signals in PB, PBB I and PBB-TE networks • Furthermore, this presentation presents some initial feedback on the tagging choice

  3. EC Type 2 support beyond PBB and EOTN • One may expect that EC Type 2 signal support will be required beyond the PBB II and EOTN networks in future; e.g. in EoSDH, EoMPLS(-TP)/VPLS, PBB-TE, PBB I and PB networks • EoSDH transports S-Tagged EC Type 1 signals via GFP-F over SDH VC-n connections; this is a similar environment as in EOTN and I+S-Tagged EC Type 2 signals would be applicable • PB, PBB-TE and PBB I transport S-Tagged EC Type 1 signals; should/could EC Type 2 signals be transported with I+S-Tags? • NOTE: EC Type 2 support in EoMPLS(-TP)/VPLS is TBA

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

  5. EC Type 1&2 supporting PEB EC Type 1 & 2 supporting Provider Edge Bridge (PEB2) Tributary Port functonality Line Port functionality S(B)-VLAN Component C-VLAN Component C-Tagged Service Interface (un-, priority-C-. C-Tagged) CNP PEP S-Tagged LANs CEP B-Com- ponent CNP PEP PNP PNP Port Based Service Interface (un- C-, priority-S- I-Tagged) PNP CNP CBP CBP To/from PEB & PEB2 & PB & PB2 & IBBEB & IBBEB2 & MEF E-NNI S-Tagged Service Interface (S-Tagged) Individual S-VLAN Service B-Com- ponent PNP PNP CNP Remote Customers C-Tagged service interface PNP CBP CBP C-VLAN Component S-VLAN Component PEP CNP CEP PAP Port-based, S- & C-Tagged Service Interface (S-, S+C-Tagged) B-Com- ponent PEP CNP PNP PNP RCAP PNP Remote Customer Port-based Service Interface CBP CBP PAP CNP EC Type 1&2 EC Type 1 Remote Customers S-Tagged Service interface PNP CNP I-Tagged service interface (I-Tagged) Individual or bundled I-Tagged Services CBP I- Component C-VLAN Component C-Tagged Service Interface (un-, priority-C-, C-Tagged) CNP PEP CBP PIP CEP PNP ports in PEB node are replaced by B-component complex to support EC Type 2 MEPs and MIPs EC Type 2 UNI-N tributary ports are added to PEB node CNP Port Based Service Interface (un-, C-, priority-S- I-Tagged) PEP CBP PIP CNP S-Tagged Service Interface (S-Tagged) CNP Remote Customers C-Tagged service interface C-VLAN Component S-VLAN Component CNP PEP CEP PAP Port-based , S- & C-Tagged Service Interface (S-, S+C-Tagged) CNP PEP RCAP Remote Customer Port-based Service Interface CNP PAP Remote Customers S-Tagged Service interface CNP PNP Transparent Service Interface (un-, C-, S-, I-Tagged) T- Component EC Type 2 CBP PIP CNP

  6. EC Type 1&2 supporting PB EC Type 1 signals EC Type 2 signals • PNP ports in PB node are replaced by B-component complex to support EC Type 2 MEPs and MIPs • NOTE: BCB node does not need to support EC Type 2 B-Com- ponent PNP PNP PNP CBP CBP PNP2 = EC Type 1 & 2 supporting PNP EC Type 1 & 2 supporting Provider Bridge (PB2) Line Port functionality Line Port functionality S(B)-VLAN Component S-Tagged LANs S-Tagged LANs B-Com- ponent B-Com- ponent PNP PNP PNP PNP PNP PNP CBP CBP CBP CBP B-Com- ponent B-Com- ponent PNP PNP PNP PNP PNP PNP CBP CBP CBP CBP B-Com- ponent B-Com- ponent PNP PNP PNP PNP PNP PNP CBP CBP CBP CBP

  7. EC Type 1&2 supporting PBB-TE IB-BEB • CNP and PIP ports in PBB-TE IB-BEB node are replaced by B-component complex to support EC Type 2 MEPs and MIPs EC Type 1 & 2 signals must pass through I-Component - ESP-MAC is not the same as B-MAC I- Component B-Com- ponent B-Com- ponent PNP PNP PNP PNP CNP EC Type 1 & 2 supporting PBB-TE IB Backbone Edge Bridge (IB-BEB2) CBP CBP CBP CBP PNP PNP B-Com- ponent B-Com- ponent PNP PNP PNP PNP CNP CBP CBP CBP CBP PNP PNP B-VLAN Component B-Tagged LANs S-Tagged LAN CBP PIP S-Tagged LAN CBP PIP I- Component B-Com- ponent B-Com- ponent S-Tagged LAN PNP PNP PNP PNP CNP CBP PIP CBP CBP CBP CBP B-Com- ponent B-Com- ponent S-Tagged LAN PNP PNP PNP PNP CNP CBP PIP CBP CBP CBP CBP

  8. EC Type 1&2 supporting PBB I IB-BEB • CNP ports in PBB I IB-BEB node are replaced by B-component complex to support EC Type 2 EC Type 2 signals can bypass I-Component PNP PNP EC Type 1 & 2 supporting PBB I IB Backbone Edge Bridge (IB-BEB2) PNP PNP B-VLAN Component B-Tagged LANs B-Com- ponent S-Tagged LAN CBP CBP CNP I- Component PIP PNP PNP CBP B-Com- ponent S-Tagged LAN PNP PIP PNP CBP CNP CBP CBP B-Com- ponent S-Tagged LAN CBP CBP CNP I- Component PIP PNP CBP CBP B-Com- ponent S-Tagged LAN PNP PIP PNP CBP CNP CBP CBP

  9. Initial feedback • I+S-Tagged EC Type 2 OAM is not acceptable • EC Type 2 OAM should be S-Tagged like EC Type 1 OAM • Use of S-Tagged EC Type 2 OAM will allow reuse of existing EC Type 1 NNI ports in packet and packet-optical transport networks • Considerations • I-Tagged LANs are not in the network/do not exist • I-Tagged Ethernet OAM (BSI OAM) is not in the network/does not exist • PBB network deployments are single domain PBB networks with S-Tagged LAN ingress/egress interfaces • No need for EC Type 2 to interwork with PIP in IB-BEB

  10. How to continue? • Ignore initial feedback and continue with I+S-Tagged EC-Type 2 OAM in standards? • Extend 802.1Q PEB, PB, PBB I IB-BEB and PBB-TE IB-BEB nodes with I+S-Tagged EC Type 2 MEP and MIP support • Let ITU-T SG15 add I+S-Tagged EC Type 2 specifications to its transport network recommendations • Build equipment with (non-standard) S-Tagged EC Type 2 OAM support • Revise our May 2011 decision? • Consider that BEBs are used only within the network, not as Network Termination (NT)/Network Interface Device (NID); i.e. BEBs have no UNI-N ports, BEBs only have NNI ports • Extend 802.1Q PEB node with EC Type 2 UNI-N ports and S-Tagged EC Type 2 OAM

  11. Backup EC Type1 and EC Type 2 examples including EC/ESP layer stack and EC/ESP identifiers EC Type1 and EC Type 2 (un)tagged primitive formats

  12. 1. PBB I and PBB-TE networkEVC(C-VLAN) via EC Type 1 S-VID Translation locations UNI • EVC = C-VLAN • EC Type 1 • S-VID Translation at PBBN domain boundaries (in CNP2) • PBB I: few mp2mp B-VLANs in each domain; B-MAC per domain • PBB-TE: full mesh of p2p TESIs in each domain; ESP-MAC per domain • no MAC address collisions in PBBN domains (multiple single-domain PBBNs) PEB2 CNP2 CNP2 CNP2 IB-BEB2 IB-BEB2 IB-BEB2 S S CEP PNP2 UNI BCB BCB B(I) B(I) B(I) S CNP2 CNP2 mp2mp B-VLAN or p2p TESI mp2mp B-VLAN or p2p TESI B(I) PEB UNI CNP2 CNP2 CNP2 IB-BEB2 IB-BEB2 IB-BEB2 S S BCB BCB CEP PNP UNI CNP B(I) B(I) B(I) UNI S PEB2 S CNP2 CNP2 CNP2 mp2mp B-VLAN or p2p TESI UNI PNP2

  13. 2. PBB I and PBB-TE networkEVC(S-VLAN) via EC Type 2 S-VID/I-SID Translation locations UNI • EVC = S-VLAN • EC Type 2, “Service B-MAC” from UNI-N to UNI-N • S-VID/I-SID Translation at PBBN domain boundaries (in CNP2) • PBB I: few mp2mp B-VLANs in each domain; B-MAC per domain • PBB-TE: full mesh of p2p TESIs in each domain; ESP-MAC per domain • no MAC address collisions in PBBN domains (multiple single-domain PBBNs) PEB2 CNP2 CNP2 CNP2 IB-BEB2 IB-BEB2 IB-BEB2 S S CEP PNP2 UNI BCB BCB B(I) B(I) B(I) S CNP2 CNP2 mp2mp B-VLAN or p2p TESI mp2mp B-VLAN or p2p TESI B(I) PEB UNI CNP2 CNP2 CNP2 IB-BEB2 IB-BEB2 IB-BEB2 S S BCB BCB CEP PNP UNI CNP B(I) B(I) B(I) UNI PEB2 S S CNP2 CNP2 CNP2 mp2mp B-VLAN or p2p TESI UNI PNP2

  14. Layer stack PB + PBB-TE forEVC(C-VLAN) via EC Type 1 S-VID is optional; typically not present in a 1:1 case C-MAC EVC C-VID EC (Type 1 and Type 2) S-VID S-VID S-VID S-VID S-VID S-VID S-VID I-SID I-SID I-SID EC(link) ESP EC ESP EC ESP EC ESP-MAC ESP-MAC ESP-MAC ESP-VID ESP-VID ESP-VID PHY PHY PHY PHY EC EC EC EC EC EC PHY PHY PHY PHY PHY PHY

  15. Layer stack PB + PBB-TE forEVC(S-VLAN) via EC Type 2 I-SID = S-VID+4096 S-VID is optional; typically not present in a 1:1 case C-VID EVC S-VID Service B-MAC EC (Type 1 and Type 2) I-SID I-SID I-SID I-SID I-SID S-VID S-VID S-VID S-VID S-VID I-SID I-SID I-SID I-SID I-SID S-VID S-VID EC ESP EC ESP EC ESP EC ESP-MAC ESP-MAC ESP-MAC ESP-VID ESP-VID ESP-VID PHY PHY PHY PHY EC EC EC EC EC EC PHY PHY PHY PHY PHY PHY

  16. Layer stack PB + PBB I forEVC(C-VLAN) via EC Type 1 S-VID is optional; typically not present in a 1:1 case C-MAC EVC C-VID EC (Type 1 and Type 2) S-VID S-VID S-VID S-VID S-VID I-SID I-SID I-SID B-MAC B-MAC B-MAC EC(link) EC(BVLAN) EC EC(BVLAN) EC EC(BVLAN) EC B-VID B-VID B-VID PHY EC EC PHY EC EC PHY EC EC PHY PHY PHY PHY PHY PHY PHY

  17. Layer stack PB + PBB I forEVC(S-VLAN) via EC Type 2 S-VID is optional; typically not present in a 1:1 case I-SID = S-VID+4096 C-VID EVC S-VID Service B-MAC EC (Type 1 and Type 2) I-SID I-SID I-SID I-SID I-SID S-VID S-VID S-VID S-VID S-VID I-SID I-SID I-SID I-SID I-SID S-VID S-VID B-MAC B-MAC B-MAC EC EC(BVLAN) EC EC(BVLAN) EC EC(BVLAN) EC B-VID B-VID B-VID PHY EC EC PHY EC EC PHY EC EC PHY PHY PHY PHY PHY PHY PHY

  18. 3. PBB II networkEVC(C-VLAN) via EC Type 1 I-SID Translation locations S-VID Translation locations UNI • EVC = C-VLAN • EC Type 1 • EC Type 1 over EC(BSI) in PBBN • S-VID Translation at PBBN network boundary (in CNP2) • I-SID Translation at PBBN domain boundaries (in CBP) • PBB II: few mp2mp B-VLANs in each domain; B-MAC per network • potential MAC address collisions in PBBN domains PEB2 CNP2 CBP CBP IB-BEB2 B-BEB B-BEB S I CEP PNP2 UNI BCB BCB B(I) B(I) B(I) I CBP CBP mp2mp B-VLAN mp2mp B-VLAN B(I) PEB UNI CNP2 CBP CBP IB-BEB2 B-BEB B-BEB S I BCB BCB CEP PNP UNI CNP B(I) B(I) B(I) UNI I PEB2 S CNP2 CBP CBP mp2mp B-VLAN UNI PNP2

  19. 4. PBB II networkEVC(S-VLAN) via EC Type 2 I-SID Translation locations S-VID Translation locations UNI • EVC = S-VLAN • EC Type 2, “Service B-MAC” from UNI-N to UNI-N • EC Type 2 over EC(BSI) in PBBN • S-VID Translation at PBBN network boundary (in CNP2) • I-SID Translation at PBBN domain boundaries (in CBP) • PBB II: few mp2mp B-VLANs in each domain; B-MAC per network • potential MAC address collisions in PBBN domains PEB2 CNP2 CBP CBP IB-BEB2 B-BEB B-BEB S I CEP PNP2 UNI BCB BCB B(I) B(I) B(I) I CBP CBP mp2mp B-VLAN mp2mp B-VLAN B(I) PEB UNI CNP2 CBP CBP IB-BEB2 B-BEB B-BEB S I BCB BCB CEP PNP UNI CNP B(I) B(I) B(I) UNI I PEB2 S CNP2 CBP CBP mp2mp B-VLAN UNI PNP2

  20. Layer stack PB + PBB II for EVC(C-VLAN) via EC Type 1 S-VID is optional; typically not present in a 1:1 case C-MAC EVC C-VID EC (Type 1 and Type 2) S-VID S-VID S-VID B-MAC EC EC(BSI) EC I-SID I-SID I-SID I-SID I-SID PHY EC(BVLAN) EC EC(BVLAN) EC EC(BVLAN) PHY B-VID B-VID B-VID EC EC PHY EC EC PHY EC EC PHY PHY PHY PHY PHY PHY

  21. Layer stack PB + PBB II for EVC(S-VLAN) via EC Type 2 I-SID = S-VID+4096 C-VID EVC S-VID Service B-MAC EC (Type 1and Type 2) I-SID I-SID I-SID I-SID I-SID I-SID I-SID S-VID S-VID EC(BVLAN) EC EC(BVLAN) EC EC(BVLAN) EC EC B-VID B-VID B-VID EC EC PHY EC EC PHY EC EC PHY PHY PHY PHY PHY PHY PHY PHY

  22. EC Type 1 Tag • S-Tagged EC Type 1 • primitive parameters • - destination_address • source_address • priority • drop_eligible • mac_service_data_unit = • EC Type 1 primitive parameters • - destination_address • source_address • priority • drop_eligible • mac_service_data_unit = TPID = 88-a8 PCP DEI S-VID Type <> 89-10 MSDU MSDU Type <> 89-10 • S-Tagged EC Type 1 • OAM primitive parameters • - destination_address • source_address • priority • drop_eligible • mac_service_data_unit = • EC Type 2 OAM primitive parameters • destination_address (=B-DA) • source_address (=B-SA) • priority • drop_eligible • mac_service_data_unit = TPID = 88-a8 PCP DEI S-VID Type = 89-02 OAM PDU Type = 89-02 OAM PDU

  23. EC Type 2 Tag • I+S-Tagged EC Type 2 • primitive parameters • -destination_address • source_address • priority • drop_eligible • mac_service_data_unit = • I-Tagged EC Type 2 • primitive parameters • destination_address • source_address • priority • drop_eligible • mac_service_data_unit = • EC Type 2 • primitive parameters • - destination_address • source_address • priority • drop_eligible • mac_service_data_unit = TPID = 88-a8 PCP DEI S-VID TPID = 88-E7 TPID = 88-E7 Type = 89-10 PCP DEI 0 Res1 Res2 I-SID PCP DEI Res1 Res2 I-SID 0 C-DA C-SA I-SID I-SID = S-VID + 4096 Type MSDU C-DA C-DA C-SA C-SA Type Type MSDU MSDU • I+S-Tagged EC Type 2 • OAM primitive parameters • -destination_address • source_address • priority • drop_eligible • mac_service_data_unit = • I-Tagged EC Type 2 • OAM primitive parameters • - destination_address • source_address • priority • drop_eligible • mac_service_data_unit = • EC Type 2 • OAM primitive parameters • destination_address • source_address • priority • drop_eligible • mac_service_data_unit = (destination address = f(B-DA,DBD) TPID = 88-a8 PCP DEI S-VID TPID = 88-E7 Type = 89-02 TPID = 88-E7 OAM PDU PCP DEI 0 Res1 Res2 I-SID PCP DEI 1 Res1 Res2 I-SID I-SID I-SID = S-VID + 4096 C-DA = B-DA C-DA = B-DA C-SA = B-SA C-SA = B-SA Type = 89-02 OAM PDU Type = 89-02 OAM PDU