Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Generalized EC Type 2 support EC Type 1&2 supporting bridges Maarten Vissers 2011-07-21 v01.

Similar presentations


Presentation on theme: "1 Generalized EC Type 2 support EC Type 1&2 supporting bridges Maarten Vissers 2011-07-21 v01."— Presentation transcript:

1 1 Generalized EC Type 2 support EC Type 1&2 supporting bridges Maarten Vissers v01

2 2 Introduction eotn-common-network-arch-0511-v01.pptxhttp://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 and based on this feedback an alternative Tagging method

3 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 4 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 I+S-Tag ? 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 I+S-Tag ? EOTN (TEB,TB, OTN XC) S-TagI+S-Tag Note: agreed in Santa Fe meeting 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 5 EC Type 1&2 supporting PEB S-Tagged LANs S(B)-VLAN Component S-VLAN Component C-VLAN Component EC Type 1 & 2 supporting Provider Edge Bridge (PEB2) CEP C-VLAN Component CEPPAP PEP CNP RCAP PNP PEP Remote Customers S-Tagged Service interface CNP CBP I-Tagged service interface (I-Tagged) I- Component CNP PIP CBP CNP C-VLAN Component CNP PEP CEP CNP S-Tagged Service Interface (S-Tagged) CNP C-Tagged Service Interface (un-, priority-C-. C-Tagged) Port Based Service Interface (un- C-, priority-S- I-Tagged) Port-based, S- & C-Tagged Service Interface (S-, S+C-Tagged) C-Tagged Service Interface (un-, priority-C-, C-Tagged) Port Based Service Interface (un-, C-, priority-S- I-Tagged) S-Tagged Service Interface (S-Tagged) Individual or bundled I-Tagged Services Individual S-VLAN Service Remote Customer Port- based Service Interface Remote Customers C-Tagged service interface T- Component CNP Transparent Service Interface (un-, C-, S-, I-Tagged) PIPCBP S-VLAN Component C-VLAN Component CEPPAP CNP RCAP PNP PEP Remote Customers S-Tagged Service interface Port-based, S- & C-Tagged Service Interface (S-, S+C-Tagged) Remote Customer Port- based Service Interface Remote Customers C-Tagged service interface Tributary Port functonality Line Port functionality To/from PEB & PEB2 & PB & PB2 & IBBEB & IBBEB2 & MEF E-NNI B-Com- ponent PNP CBP B-Com- ponent PNP CBP B-Com- ponent PNP CBP EC Type 1 EC Type 2 EC Type 1&2 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

6 6 S(B)-VLAN Component EC Type 1 & 2 supporting Provider Bridge (PB2) B-Com- ponent S-Tagged LANs PNP Line Port functionality PNP CBP B-Com- ponent PNP CBP B-Com- ponent S-Tagged LANs PNP Line Port functionality PNP CBP B-Com- ponent PNP CBP B-Com- ponent PNP CBP B-Com- ponent PNP CBP EC Type 1&2 supporting PB 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 CBP PNP PNP2 = EC Type 1 & 2 supporting PNP EC Type 1 signals EC Type 2 signals

7 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 B-Tagged LANs B-VLAN Component EC Type 1 & 2 supporting PBB-TE IB Backbone Edge Bridge (IB-BEB2) PNP I- Component B-Com- ponent PNP CBP B-Com- ponent PNP CBP B-Com- ponent CNP PNP CBP B-Com- ponent CNP PNP CBP PIP CBP S-Tagged LAN PNP I- Component B-Com- ponent PNP CBP B-Com- ponent PNP CBP B-Com- ponent CNP PNP CBP B-Com- ponent CNP PNP CBP PIP CBP S-Tagged LAN EC Type 1 & 2 signals must pass through I-Component -ESP-MAC is not the same as B-MAC

8 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 B-Tagged LANs B-VLAN Component EC Type 1 & 2 supporting PBB I IB Backbone Edge Bridge (IB-BEB2) PNP I- Component B-Com- ponent CNP CBP PNP B-Com- ponent CNP PNP CBP PIP CBP S-Tagged LAN PNP S-Tagged LAN CBP I- Component B-Com- ponent CNP CBP PNP CBP B-Com- ponent CNP PNP CBP PIP CBP EC Type 2 signals can bypass I-Component

9 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 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 11 Alternative solution

12 12 Alternative for the May 2011 Solution Deploy the I-Component plus one or more CBPs as UNI-N tributary port functionality for EC Type 2 Add those UNI-N ports to PEB nodes Use “B-VLAN MEP” functions on CBP to generate/terminate S-Tagged EC Type 2 OAM Do not use BSI MEP and MIP functions I-Tag is part of EVC encapsulation No changes to other nodes necessary; i.e. a backwards compatible solution

13 13 Alternative EC frame tagging in PB, PBB, PBB-TE, EOTN NetworkEC Type 1 tagEC Type 2 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 S-Tag Note: in B-VLAN an I-Tag or S+I- Tag is used 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 S-Tag Note: Inside PBB network the EC frames are carried inside a 2 nd EC frame, which is I-Tagged PB + PBB-TE (PEB, PB, IB-BEB, BCB) S-Tag Note: in ESP an I-Tag or S+I-Tag is used S-Tag Note: in ESP an I-Tag or S+I-Tag is used EOTN (TEB,TB, OTN XC) S-TagI+S-Tag Note: agreed in Santa Fe meeting 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

14 14 Alternative EC Type 1&2 supp. PEB S-Tagged LANs S-VLAN Component S-VLAN Component C-VLAN Component EC Type 1 & 2 supporting Provider Edge Bridge CEP C-VLAN Component CEPPAP PEP CNP RCAP PNP PEP Remote Customers S-Tagged Service interface CNP CBP I-Tagged service interface (I-Tagged) I- Component CNP PIP CBP CNP C-VLAN Component CNP PEP CEP CNP S-Tagged Service Interface (S-Tagged) CNP C-Tagged Service Interface (un-, priority-C-. C-Tagged) Port Based Service Interface (un- C-, priority-S- I-Tagged) Port-based, S- & C-Tagged Service Interface (S-, S+C-Tagged) C-Tagged Service Interface (un-, priority-C-, C-Tagged) Port Based Service Interface (un-, C-, priority-S- I-Tagged) S-Tagged Service Interface (S-Tagged) Individual or bundled I-Tagged Services Individual S-VLAN Service Remote Customer Port- based Service Interface Remote Customers C-Tagged service interface T- Component CNP Transparent Service Interface (un-, C-, S-, I-Tagged) PIPCBP S-VLAN Component C-VLAN Component CEPPAP CNP RCAP PNP PEP Remote Customers S-Tagged Service interface Port-based, S- & C-Tagged Service Interface (S-, S+C-Tagged) Remote Customer Port- based Service Interface Remote Customers C-Tagged service interface Tributary Port functonality Line Port To/from PEB & PEB2 & PB & PB2 & IBBEB & IBBEB2 & MEF E-NNI PNP EC Type 1 EC Type 2 EC Type 1&2 Regular PNP ports are capable to support EC Type 1 & 2 EC Type 2 UNI-N tributary ports are added to PEB node

15 15 EVC into EC Type 2 encapsulation S-VID/PCP/DEI preserved, Individual or Bundled S-VLAN service EC Type 2 primitive parameters - destination_address - source_address - priority - drop_eligible - vlan_identifier - mac_service_data_unit = C-DA C-SA MSDU Type S-VIDPCP DEI TPID = 88-a8 S-Tagged EVC primitive parameters -destination_address - source_address - priority - drop_eligible - mac_service_data_unit = TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID = ?? C-DA C-SA MSDU Type S-VIDPCP DEI TPID = 88-a8 S-VID, S-PCP, S-DEI preserved What value should the ISID have? ISID is only visible in the EC Type 2 UNI-N tributary ports in PEB nodes Options: 1)Fixed ISID value 2)ISID locked to customer’s SVID 3)Configurable ISID

16 16 EVC into EC Type 2 encapsulation S-VID/PCP/DEI not preserved, Individual S-VLAN service EC Type 2 primitive parameters - destination_address - source_address - priority - drop_eligible - mac_service_data_unit = C-DA C-SA MSDU Type S-VIDPCP DEI TPID = 88-a8 S-Tagged EVC primitive parameters -destination_address - source_address - priority - drop_eligible - mac_service_data_unit = TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID = ?? C-DA C-SA MSDU Type C-DA C-SA MSDU Type untagged EVC primitive parameters -destination_address - source_address - priority - drop_eligible - vlan_identifier - mac_service_data_unit = EC Type 2 OAM primitive parameters - destination_address - source_address - priority - drop_eligible - mac_service_data_unit = OAM PDU Type = What value should the ISID have? ISID is only visible in the EC Type 2 UNI-N tributary ports in PEB nodes Options: 1)Fixed ISID value 2)Configurable ISID

17 17 EVC into EC Type 2 encapsulation Transparent service EC Type 2 primitive parameters - destination_address - source_address - priority - drop_eligible - mac_service_data_unit = C-DA C-SA MSDU Type S-VIDPCP DEI TPID = 88-a8 Transparent EVC primitive parameters -destination_address - source_address - priority - drop_eligible - mac_service_data_unit = TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID = ?? C-DA C-SA MSDU Type S-VIDPCP DEI TPID = 88-a8 OAM PDU Type = C-DA C-SA OAM PDU Type = TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID = ?? C-DA C-SA OAM PDU Type = What value should the ISID have? ISID is only visible in the EC Type 2 UNI-N tributary ports in PEB nodes Options: 1)Fixed ISID value 2)Configurable ISID What value should the ISID have? ISID is only visible in the EC Type 2 UNI-N tributary ports in PEB nodes Options: 1)Fixed ISID value 2)Configurable ISID EC Type 2 OAM primitive parameters - destination_address - source_address - priority - drop_eligible - mac_service_data_unit =

18 18 EC Type 2 Tag EC Type 2 primitive parameters - destination_address - source_address - priority - drop_eligible - vlan_identifier - mac_service_data_unit = EC Type 2 OAM primitive parameters - destination_address - source_address - priority - drop_eligible - vlan_identifier - mac_service_data_unit = OAM PDU Type = S-VIDPCP DEI TPID = 88-a8 TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID = ?? OAM PDU Type = S-VIDPCP DEI TPID = 88-a8 S-Tagged EC Type 2 primitive parameters -destination_address - source_address - priority - drop_eligible - mac_service_data_unit = S-Tagged EC Type 2 OAM primitive parameters -destination_address - source_address - priority - drop_eligible - mac_service_data_unit = TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID = ?? C-DA C-SA MSDU Type C-DA C-SA MSDU Type

19 19 I-SID value Option I Backbone Service Instance Table (c6.11 CBP function) Backbone- VID Backbone- SID Local-SIDDefault Backbone Destination A A B B C C D D E E Backbone Service Instance Table (c6.10 PIP function) VIP-ISSVIP-ISIDDefault Backbone Destination adminPointTo PointMAC enableConne ctionIdentifier A4096+A B4096+B C4096+C D4096+D E4096+E VIP-ISID and Local- SID parameters have local significance only; no need to coordinate I-SID value with other EC Type 2 UNI-N ports Text in c supports this approach. Text in c seems not to support this approach; B-SIDs must be unique as B-VID is not used in row selection process. Correct?

20 20 I-SID value Option II Backbone Service Instance Table (c6.11 CBP function) Backbone-VIDBackbone-SID ABCa DEFb GHIc JKLd MNOe Backbone Service Instance Table (c6.10 PIP function) VIP-ISSVIP-ISIDDefault Backbone Destination adminPointTo PointMAC enableConne ctionIdentifier Aa Bb Cc Dd Ee VIP-ISID/Backbone-SID values must be negotiated amongst the EC Type 2 UNI-N ports High probability that the M (2≤M≤8192) UNI-N ports in EC Type 2 have at least one I-SID value available

21 21 Backup I+S-Tagged EC Type 2 (May 2011 solution) 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

22 22 1. PBB I and PBB-TE network EVC(C-VLAN) via EC Type 1 PEB2 BC B IB-BEB2 CNP2 PNP2 IB-BEB2 BC B CNP2 S S S B(I) UNI B(I) BC B IB-BEB2 CNP2 S S B(I) BC B I B-BEB2 B(I) CEP CNP2 mp2mp B-VLAN or p2p TESI mp2mp B-VLAN or p2p TESI mp2mp B-VLAN or p2p TESI 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) S-VID Translation locations PEB PNP UNI CEP S PEB2 PNP2 S UNI CNP

23 23 2. PBB I and PBB-TE network EVC(S-VLAN) via EC Type 2 PEB2 BC B IB-BEB2 CNP2 PNP2 IB-BEB2 BC B CNP2 S S S B(I) UNI B(I) BC B IB-BEB2 CNP2 S S B(I) BC B I B-BEB2 B(I) CEP CNP2 mp2mp B-VLAN or p2p TESI mp2mp B-VLAN or p2p TESI mp2mp B-VLAN or p2p TESI S-VID/I-SID Translation locations PEB PNP UNI CEP S PEB2 PNP2 S UNI CNP 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)

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

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

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

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

28 28 3. PBB II network EVC(C-VLAN) via EC Type 1 PEB2 BC B IB-BEB2 CNP2 PNP2 B-BEB BC B CBP S I I B(I) UNI B(I) BC B B-BEB CBP I I B(I) BC B I B-BEB2 B(I) CEP CNP2 mp2mp B-VLAN 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 S-VID Translation locations PEB PNP UNI CEP S PEB2 PNP2 S UNI CNP I-SID Translation locations

29 29 4. PBB II network EVC(S-VLAN) via EC Type 2 PEB2 BC B IB-BEB2 CNP2 PNP2 B-BEB BC B CBP S I I B(I) UNI B(I) BC B B-BEB CBP I I B(I) BC B I B-BEB2 B(I) CEP CNP2 mp2mp B-VLAN 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 S-VID Translation locations PEB PNP UNI CEP S PEB2 PNP2 S UNI CNP I-SID Translation locations

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

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

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

33 33 EC Type 2 Tag EC Type 2 primitive parameters - destination_address - source_address - priority - drop_eligible - mac_service_data_unit = C-DA C-SA MSDU Type = Type EC Type 2 OAM primitive parameters - destination_address - source_address - priority - drop_eligible - mac_service_data_unit = OAM PDU Type = 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 TPID = 88-E7 I-SIDPCP DEI Res2 1 Res1 I-SID = S-VID C-DA = B-DA C-SA = B-SA OAM PDU Type = S-VIDPCP DEI TPID = 88-a8 I+S-Tagged EC Type 2 primitive parameters -destination_address - source_address - priority - drop_eligible - mac_service_data_unit = I+S-Tagged EC Type 2 OAM primitive parameters -destination_address - source_address - priority - drop_eligible - mac_service_data_unit = TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID C-DA C-SA MSDU Type TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID C-DA = B-DA C-SA = B-SA OAM PDU Type = I-Tagged EC Type 2 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 = (destination address = f(B-DA,DBD)

34 34 Backup S-Tagged EC Type 2 (Proposed July 2011 solution) 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

35 35 To be added in v02


Download ppt "1 Generalized EC Type 2 support EC Type 1&2 supporting bridges Maarten Vissers 2011-07-21 v01."

Similar presentations


Ads by Google