1 / 43

E-OTN status update and service interface question [associated with ITU-T liaison statement liaison-itut-sg15-ols-277-0

E-OTN status update and service interface question [associated with ITU-T liaison statement liaison-itut-sg15-ols-277-0311 ] version 01. Maarten Vissers 2011-03-15. New slides : 40 (EVC EC.. Relations) , 41/42/43 (I- to S-Tag interworking principle)

bryce
Download Presentation

E-OTN status update and service interface question [associated with ITU-T liaison statement liaison-itut-sg15-ols-277-0

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. E-OTN status update and service interface question[associated with ITU-T liaison statementliaison-itut-sg15-ols-277-0311] version 01 Maarten Vissers 2011-03-15 New slides: 40 (EVCEC.. Relations), 41/42/43 (I- to S-Tag interworking principle) Enhanced slides: 6 (TEB, TB name explanation), 7/15/16/17 ((E)NNI links extended into Eth Services layer, 12/35 (area E: transport NNI port area)

  2. Contents • Introduction • G.8012 • EOTN • Ethernet Services in EOTN • Ethernet services support in Transport Edge Bridge • MAC-in-MAC encapsulated Ethernet services • Hybrid EOTN – PBBN EC options • EC frame format options • PBBN B-Tagged LAN frame formats • What is the best option? • Annex • OTN Network Port functionality • ODUk with GFP encapsulated S-Tagged Ethernet frames • Transport Bridge model (802.1Q style) • Hybrid PB, PBB, PBB-TE, EOTN network example • EVC  EC  B-VLAN/ESP/ODU/… relationships • I-Tagged EC to S-Tagged EC interworking function principle

  3. Introduction

  4. IntroductionG.8012 Study is underway in Question 10 of ITU-T Study Group 15 (Q10/15) on what additions to ITU-T Rec. G.8012 “Ethernet UNI and NNI” would be required to support all MEF services and 802.1 service interfaces for Ethernet over OTN (Optical Transport Network) MEF terms “Ethernet Virtual Connection” (EVC) and “Ethernet Connection” (EC) will be used in G.8012 and other ITU-T Ethernet recommendations (e.g. G.8010, G.8011 series) to identify the customer and network service instances G.8012 is to be extended with descriptions of the set of EVC types “EVC to EC” mappings; one mapping per EVC type EC frame format “EC to ODU” mapping “EC to E-NNI” mapping (MEF26 compliant) Additional “EC to …” mappings as needed; e.g. “EC to SDH VC-n”, “EC to PBB B-VLAN”, “EC to PBB-TE ESP”, …

  5. Introduction EOTN Progress has been made in the definition of the Ethernet OTN (EOTN) network in Question 9 and 10 of ITU-T Study Group 15 during their Dec 2010 and Feb 2011 meetings The T-VLAN Tag proposal has been withdrawn S-Tags will be used on the EOTN internal interfaces to identify the EC signals (i.e. Service VLAN signals) when those are multiplexed into point-to-point OTN ODU connections See slides 33 and 34 for frame format and OTN Network Port (ONP) functionality The ECs carry any type of EVC, where necessary with the use of MAC-in-MAC The ODUs carry EC signal aggregates The ODUs within an EOTN network perform as such the role of mp2mp Backbone VLANs in a PB/PBB network and of p2p ESPs in a PB/PBB-TE network Note that the EOTN does not contain Backbone VLANs or ESPs

  6. IntroductionEOTN Ordering , Provisioning, Billing, Management and Support Management Plane Application Services Layer Control Plane Data Plane Ethernet Services Layer • The EOTN architecture is aligned withMEF’s Global Interconnect architecture • The EOTN includes: • an “Ethernet Services layer” which provides for S-Tagged ECs; each ECcarries one EVC • an OTN based “Transport Services layer” in which point-to-point ODU connections carry aggregates of those S-Tagged ECs between “Transport Bridges” (TB) and “Transport Edge Bridges” (TEB) (see slides 7, 12, 35) • TEB is a “PEB with transport NNI ports and additional UNI-N ports” • TB is a “PB with transport NNI ports” • TB/TEBs also support Provider Network Ports (PNP) to connect – via MEF E-NNIs – to other carrier networks either directly, or indirectly via a “Carrier Ethernet Exchange” (CEX) Transport Services Layer

  7. IntroductionEOTN TB/TEBs may also contain other types of transport network ports; e.g. SDH, MPLS-TP, …This is not further addressed in this presentation Transport Edge Bridges (TEB) interconnected via Transport Bridges (TB) Customer MA Ethernet Services Layer Provider MA Operator MA Operator MA TEBs and TBs interconnected via Transport UNI UNI Transport Services Layer OTN SDH OTN ETH NNI OTN ENNI ENNI TEB TB TEB TB CEX TB TB TB TB Note 1: E-NNI links are typically be monitored using Link MEPs. Note 2: Ethernet Service MEPs may be used in addition on E-NNIs to monitor fault/performance on a per Ethernet Connection basis. CEX: Carrier Ethernet Exchange TEB: Transport Edge Bridge TB: Transport Bridge

  8. IntroductionEOTN vs PBN/PBBN The EOTN provides a flat Ethernet architecture containing a single Service VLAN layer providing for S-Tagged ECs The EOTN differs here from the PBN/PBBN architecture which contains two service layers: Service VLAN layer providing for S-Tagged ECs, and Backbone Service Instance layer providing for I-Tagged ECs There are several options in defining the MAC-in-MAC encapsulation of transparent and bundled C-/S-VLAN services into the single Service VLAN layer in the EOTN ITU-T SG15 is requesting IEEE 802.1’s advice which option to select Slide 26 presents the options for individual service case Slide 27 presents the options for bundled service case

  9. Ethernet Services in EOTN

  10. Ethernet Services Overview UNI Link EPL services supported in SDH, OTN Frame Based Ethernet Services in EOTN C-Tagged or S-Tagged or I-Tagged or B-Tagged Ethernet services UnTagged or Priority-Tagged Ethernet services UNI Link UNI Link UNI Link S- + C-Tagged or B- + I-Tagged Ethernet services Ethernet service Ethernet service (V-)UNILink UNI Link UNI Link UNI Link Ethernet service Ethernet service Ethernet service UNI Link UNI Link UNI Link (V-)UNILink Ethernet service Ethernet service Ethernet service Ethernet service • Transparent service • Port based service • Two port MAC relay service • C-Tagged service • S/B-Tagged service • I-Tagged service • C-Tagged service • I-Tagged service Bit/CodeWord stream service G.8011.x service types EPL Type 2EPL Type 2/TT EPL Type 1, EVPL Type 2EPT, EVPT Type 2 EPLAN, EVPLAN Type 2 EVPL Type 1/3EVPT Type 1/3EVPLAN Type 1/3 EVPL Type 1/3EVPT Type 1/3EVPLAN Type 1/3

  11. Ethernet Services • Ethernet services are supported in the EOTN by its S-Tagged ECs • port-based, individual C-VLAN, bundled C-VLAN and individual S-VLAN services are supported in the same manner as in a PB network, and a TEB includes the PEB functionality (see “A” in slide 12) • Interoperability between EC endpoints in TEB and PEB nodes is provided naturally • p2p and mp bundled BSI services are supported via a B-VLAN which is deployed as a S-VLAN (see “B” in slide 12) • p2p and mp bundled S-VLAN and transparent services are supported by means of a MAC-in-MAC encapsulation, MAC-in-MAC encapsulation may also be deployed for e.g. mp bundled C-VLAN services (see “C” in slide 12)

  12. Transport Edge Bridge Line Ports Tributary Port functonality Ethernet Services support in Transport Edge Bridge S-VLAN Component C-VLAN Component C-Tagged Service Interface (un-, priority-C-. C-Tagged) CNP PEP S-Tagged LANs CEP CNP PEP To/from PEB & PB & IBBEB & MEF E-NNI Port Based Service Interface (un- C-, priority-S- I-Tagged) PNP CNP S-Tagged Service Interface (S-Tagged) Individual S-VLAN Service CNP PNP Remote Customers C-Tagged service interface C-VLAN Component S-VLAN Component PEP CNP ? CEP PAP Port-based, S- & C-Tagged Service Interface (S-, S+C-Tagged) To/from IBEB & TBEB & BBEB ??? PEP CNP RCAP Remote Customer Port-based Service Interface D PAP CNP ??? A Remote Customers S-Tagged Service interface PNP CNP I-Tagged service interface (I-Tagged) Interworking function Individual or bundled I-Tagged Services CBP B ? ONP I- Component C-VLAN Component OTN ADMs/XCs (P2P ODUs) C-Tagged Service Interface (un-, priority-C-, C-Tagged) CNP PEP CNP PIP CEP ONP 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 SDH ADMs/XCs (P2P VCs) C-VLAN Component SNP S-VLAN Component CNP PEP CEP PAP Port-based , S- & C-Tagged Service Interface (S-, S+C-Tagged) SNP CNP PEP RCAP Remote Customer Port-based Service Interface C CNP PAP MPLS-TP P nodes (P2P transport-LSPs) MTNP Remote Customers S-Tagged Service interface CNP PNP MTNP T- Component Transparent Service Interface (un-, C-, S-, I-Tagged) ? E CNP CNP PIP T- Component Transparent Service Interface (un-, C-, S-, I-Tagged) CBP PIP CNP

  13. MAC-in-MAC encapsulatedEthernet Services • The encapsulation format for those MAC-in-MAC encapsulated services (“C” in slide 9) is however not yet clear, because the EOTN deploys S-Tagged ECs and the PBBN deploys I-Tagged ECs • Multiple encapsulation formats have been identified (see slides 20 to 27) • A single, common encapsulation format applicable in PBN/PBBN and EOTN is preferred to support point-to-point ECs and multipoint ECs with endpoints in both the EOTN and PB/PBB networks. E.g. for a • p2p or mp bundled S-VLAN service it’s EC may have endpoints in TEB, I-BEB and IB-BEB nodes • p2p transparent service its EC may have endpoints in TEB and T-BEB or TB-BEB nodes

  14. Hybrid EOTN – PBBN EC options

  15. Hybrid EOTN-PBBN EC (option 1) S-Tagged EC segment I-Tagged EC segment Customer MA Ethernet Services Layer EC Provider MA Operator MA Operator MA PBBN UNI UNI Transport Services Layer OTN OTN OTN I-LAN ENNI ENNI TEB TB IBEB TB CEX TB TB BBEB BBEB Interworking function • To support a hybrid EOTN-PBBN EC with endpoints in a TEB and I-BEB, an interworking function would be required to connect the I-Tagged EC segment in the PBBN with the S-Tagged EC segment in the EOTN • Such interworking function should support the EC Provider MA, which has endpoints in the edge bridges in both the PBB and EOTN networks • In figure below EC Provider MA endpoints are in TEB and I-BEB (PIP) CEX: Carrier Ethernet Exchange TEB: Transport Edge Bridge TB: Transport Bridge

  16. Hybrid EOTN-PBBN EC (option 2) S-Tagged EC S-Tagged EC segment Customer MA Ethernet Services Layer EC Provider MA Operator MA Operator MA UNI UNI P(B)BN Transport Services Layer OTN NNI OTN OTN ENNI ENNI IB BEB PB(BCB) TEB PB(BCB) CEX TB TB TB TB • An alternative option to establish a hybrid PBBN-EOTN EC would be to deploy a Backbone VLAN as a “Service VLAN” • Suggested in 802.1 meeting in Nov. 2010 • Such “Service VLAN” would carry e.g. a single bundled S-VLAN service or a single Transparent service • In figure below EC Provider MA endpoints are in IB-BEB (CBP) and TEB • PBBN has become a PBN in this case as there is no service aggregation CEX: Carrier Ethernet Exchange TEB: Transport Edge Bridge TB: Transport Bridge

  17. Hybrid EOTN-PBBN EC (option 2) Two IB-BEBs S-Tagged EC S-Tagged EC segment Customer MA Ethernet Services Layer EC Provider MA Operator MA Operator MA NNI UNI UNI PBBN Transport Services Layer OTN NNI OTN OTN ENNI ENNI IB BEB1 IB BEB2 IB BEB3 TEB BCB CEX TB TB TB TB An alternative means to deploy a Backbone VLAN as a Service VLAN is to deploy an additional IB-BEB for the EVC to EC mapping IB-BEB1 performs the EVC to EC mapping and generates an S-Tagged EC signal, IB-BEB2 performs the EC to B-VLAN aggregation CEX: Carrier Ethernet Exchange TEB: Transport Edge Bridge TB: Transport Bridge

  18. Hybrid EOTN-PBBN EC comparison Option 1 Option 2 EC endpoints can be in EOTN TEBs, PBBN IB-BEBs and TB-BEBs EC endpoints cannot be in I-BEBs or T-BEBs I-Tagged ECs are not supported outside BVLANs IB-BEBs and TB-BEBs can not support both the EC endpoint for S-VLAN/ transparent service and the B-VLAN endpoint over which this EC is carried No interworking function required • EC endpoints can be in EOTN TEBs, PBBN I-BEBs, IB-BEBs, T-BEBs and TB-BEBs • Multi domain PBBNs • I-Tagged LANs supported • Requires interworking function to interconnect S-Tagged EC segment with I-Tagged EC segment • IW function has to convert I-Tag into S-Tag and vice versa • IW function located in ports in area D in slide 12 Acceptable for PB/PBBN?

  19. EC Frame Format Options

  20. Option 1 and 2 EC Frame Formats I-SID= 0 0 0 0 0 0 0 0 0 0 0 1 VID • EC Frame formats associated with Option 1 are presented in slides 21, 22, 23 • Slide 21: individual service (e.g. C-VLAN, S-VLAN, port-based, transparent) • Slide 22: bundled C-/S-VLAN service • Slide 23: EC OAM • EC Frame formats associated with Option 2 are presented in slides 24, 25 • Slide 24: EC OAM • Slide 24: individual service • Slide 25: bundled C-/S-VLAN service has two options • Option 2A: C-Tag [S-Tag] is maintained in the frame format, I-Tag with fixed I-SID value is added • Option 2B: C-Tag [S-Tag] is replaced by I-Tag and I-SID value is a function of the C-VID [S-VID]; e.g. I-SID=4096+VID

  21. Option 1 EC Frame FormatsIndividual service B-DA 6 B-SA 6 TPID = 88-a8 B-DA 2 6 PCP DEI S-VID B-SA 6 2 Frame format in EOTN Type = 89-10 Type = 89-10 2 2 C-DA C-DA C-DA C-SA C-SA C-SA Type Type MSDU Type MSDU MSDU EVC Frame N octets EC Frame (= BSI Frame) N+14 octets S-Tagged EC Frame N + 18 octets B-DA 6 B-SA 6 TPID = 88-E7 B-DA 2 6 PCP DEI 0 Res1 Res2 I-SID B-SA 6 2 Frame format in PBBN Type = 89-10 I-SID 2 2 C-DA C-DA C-DA C-SA C-SA C-SA Type Type Type MSDU MSDU MSDU EVC Frame N octets EC Frame (=BSI Frame) N+14 octets I-Tagged EC Frame N+18 octets

  22. Option 1 EC Frame Formats Bundled C-/S-VLAN service 6 B-DA 6 B-SA 6 2 TPID = 88-a8 B-DA 6 2 PCP DEI S-VID B-SA 2 2 Type = 89-10 Type = 89-10 Frame format in EOTN C-DA C-DA C-DA C-SA C-SA C-SA 2 TPID = 81-00 or 88-a8 2 TPID = 81-00 or 88-a8 2 TPID = 81-00 or 88-a8 2 PCP X VID 2 PCP X VID 2 PCP X VID Type Type MSDU MSDU MSDU Type C-/S-Tagged EVC Frame N+4 octets EC Frame (= BSI Frame) N+18 octets S-Tagged EC Frame N+22 octets 6 B-DA X: CFI or DEI 6 B-SA TPID = 88-E7 6 B-DA 2 PCP DEI 0 Res1 Res2 I-SID 6 2 B-SA 2 Type = 89-10 I-SID 2 Frame format in PBBN 6 C-DA C-DA C-DA 6 C-SA C-SA C-SA 2 2 TPID = 81-00 or 88-a8 TPID = 81-00 or 88-a8 2 TPID = 81-00 or 88-a8 2 2 PCP X VID PCP X VID 2 PCP X VID Type Type Type MSDU MSDU MSDU C-/S-Tagged EVC Frame EC Frame (=BSI Frame) I-Tagged EC Frame N+22 octets

  23. Option 1 EC OAM Frame Formats 6 B-DA 6 B-SA Frame format in EOTN 2 6 B-DA TPID = 88-a8 6 2 B-SA PCP DEI S-VID Type = 89-02 Type = 89-02 OAM PDU Type = 89-02 OAM PDU OAM PDU OAM PDU M octets EC OAM Frame M+12 octets S-Tagged EC OAM Frame M+16 octets 6 B-DA = f(B-DA,DBD) 6 B-SA TPID = 88-E7 2 PCP DEI 0 Res1 Res2 I-SID 2 2 I-SID = f(ETH_FP) Frame format in PBBN 6 6 B-DA C-DA = B-DA 6 6 B-SA C-SA = B-SA Type = 89-02 Type = 89-02 Type = 89-02 OAM PDU OAM PDU OAM PDU OAM PDU M octets EC OAM Frame M+12 octets I-Tagged EC OAM Frame M+30 octets

  24. Option 2 EC & EC OAM Frame FormatsIndividual service B-DA 6 6 B-SA B-DA Frame format in EOTN & PBBN 6 2 TPID = 88-a8 B-SA 6 2 PCP DEI S-VID Type = 89-02 Type = 89-02 OAM PDU OAM PDU OAM PDU Type = 89-02 OAM PDU M octets EC OAM Frame M+12 octets S-Tagged EC OAM Frame M+16 octets 6 B-DA 6 B-SA B-DA 6 2 TPID = 88-a8 B-SA 6 2 PCP DEI S-VID TPID = 88-E7 TPID = 88-E7 2 2 PCP DEI 0 Res1 Res2 I-SID PCP DEI 0 Res1 Res2 I-SID 2 2 Frame format in EOTN & PBBN I-SID = fixed value 2 I-SID = fixed value 2 C-DA C-DA C-DA C-SA C-SA C-SA Type Type MSDU MSDU Type MSDU EVC Frame N octets EC Frame (= B-VLAN Frame) N+18 octets S-Tagged EC Frame N+22 octets

  25. Option 2 EC Frame FormatsBundled C-/S-VLAN service 6 B-DA 6 B-SA 2B 2 6 B-DA TPID = 88-a8 6 2 PCP DEI S-VID B-SA TPID = 88-E7 TPID = 88-E7 2 2 Frame format in EOTN & PBBN PCP DEI 0 Res1 Res2 I-SID 2 2 PCP DEI 0 Res1 Res2 I-SID C-DA 2 I-SID = e.g. 4096 + VID 2 I-SID = e.g. 4096 + VID C-SA 2 C-DA C-DA TPID 2 C-SA C-SA PCP X VID Type Type MSDU MSDU MSDU Type S-Tagged EC Frame (N+22 octets) C-/S-Tagged EVC Frame N+4 octets EC Frame (= B-VLAN Frame) N+18 octets 6 B-DA 6 B-SA B-DA 6 2 TPID = 88-a8 B-SA 6 2 PCP DEI S-VID 2A TPID = 88-E7 TPID = 88-E7 2 2 PCP DEI 0 Res1 Res2 I-SID PCP DEI 0 Res1 Res2 I-SID 2 2 Frame format in EOTN & PBBN I-SID = fixed value 2 I-SID = fixed value 2 C-DA C-DA C-DA C-SA C-SA C-SA 2 2 TPID 2 TPID TPID 2 2 PCP X VID 2 PCP X VID PCP X VID Type Type MSDU Type MSDU MSDU C-/S-Tagged EVC Frame EC Frame (= B-VLAN Frame) S-Tagged EC Frame (N+26 octets)

  26. S-Tagged EC Frame format in EOTN comparison - Individual service Option 2 Option 1 6 B-DA 6 B-SA B-DA 6 2 TPID = 88-a8 B-SA 6 2 PCP DEI S-VID TPID = 88-E7 2 TPID = 88-a8 2 PCP DEI 0 Res1 Res2 I-SID 2 2 PCP DEI S-VID 2 2 I-SID = fixed value Type = 89-10 C-DA C-DA C-SA C-SA Type Type MSDU MSDU S-Tagged EC Frame N + 18 octets Difference 4 octets S-Tagged EC Frame N+22 octets Difference in frame formats is in the red boxes

  27. S-Tagged EC Frame format in EOTN comparison - Bundled C-/S-VLAN service Option 2A Option 1 Option 2B B-DA 6 B-SA 6 B-DA B-DA TPID = 88-a8 6 6 2 B-SA B-SA PCP DEI S-VID 6 6 2 TPID = 88-a8 TPID = 88-E7 TPID = 88-a8 2 2 2 PCP DEI S-VID PCP DEI 0 Res1 Res2 I-SID PCP DEI S-VID 2 2 2 TPID = 88-E7 I-SID = fixed value Type = 89-10 2 2 2 PCP DEI 0 Res1 Res2 I-SID C-DA C-DA 2 I-SID = e.g. 4096 + VID C-SA C-SA 2 C-DA TPID = 81-00 or 88-a8 TPID 2 2 C-SA PCP X VID PCP X VID 2 2 Type Type MSDU Type MSDU MSDU S-Tagged EC Frame N+22 octets Difference 0 octets S-Tagged EC Frame N + 22 octets Difference 4 octets S-Tagged EC Frame N+26 octets Difference in frame formats is in the red and green boxes 27

  28. PBBN B-Tagged LAN Frame Formats

  29. PBB networkOption 1 frame format • Option 1 frame format on a B-Tagged LAN is the regular 802.1ah frame format with • One B-DA • One B-SA • One B-Tag • One I-Tag PBBN B-Tagged LAN Frame Format 6 B-DA EC’s B-DA/SA 6 B-SA 2 TPID = 88-a8 PBBN B-VLAN B-Tag 2 PCP DEI B-VID TPID = 88-E7 2 EC BSI I-Tag EVC encaps I-Tag PCP DEI 0 Res1 Res2 I-SID 2 2 I-SID C-DA C-SA Type MSDU EVC Frame B(I)-Tagged EC Frame N+22 octets

  30. PBB networkOption 2 – frame formats IB-BEB2 PIP inserts S-Tag and I-Tag IB-BEB2 PIP inserts I-Tag only PBBN B-Tagged LAN Frame Format IB-BEB2 PBBN B-Tagged LAN Frame Format 6 B-DA PBBN B-DA/SA 6 B-SA 6 2 B-DA TPID = 88-a8 PBBN B-DA/SA PBBN B-VLAN B-Tag 6 2 B-SA PCP DEI B-VID 2 2 TPID = 88-a8 TPID = 88-E7 PBBN B-VLAN B-Tag PBBN BSI I-Tag 2 2 PCP DEI B-VID PCP DEI 0 Res1 Res2 I-SID 2 2 TPID = 88-E7 I-SID PBBN EC I-Tag 2 PCP DEI 0 Res1 Res2 I-SID 6 B-DA EC’s B-DA/SA 2 I-SID 6 B-SA 6 B-DA 2 TPID = 88-a8 EC’s S-Tag EC’s B-DA/SA 6 B-SA 2 PCP DEI S-VID IB-BEB1 TPID = 88-E7 TPID = 88-E7 2 2 EVC encaps I-Tag EVC encaps I-Tag PCP DEI 0 Res1 Res2 I-SID PCP DEI 0 Res1 Res2 I-SID 2 2 2 I-SID = fixed value 2 I-SID = fixed value C-DA C-DA C-SA C-SA Type Type MSDU MSDU EVC Frame B(I)-Tagged EC Frame N+40 octets B(I(S))-Tagged EC Frame N+44 octets Difference with Option 1 is 22 octets Difference with Option 1 is 18 octets

  31. What is the best option? • Option 1? • If option 1, then who should describe the I-Tagged EC to S-Tagged EC interworking function: ITU-T SG15 as part of its EOTN work, or IEEE 802.1? • Note: interworking function can also be deployed to interconnect PBBN via MEF26 E-NNI to EOTN • Option 2? • If option 2, then which bundled service frame format option should be used? Option 2A or Option 2B? • If option 2, will I-Tagged LAN, I-BEB, T-BEB and B-BEB in 802.1Q be deprecated, or will 802.1Q be adapted to indicate that BSI is not used as EC, that I-/T-BEBs are not supporting UNIs and that two IB-BEBs are needed to support bundled S-VLAN and transparent EVCs?

  32. Annex

  33. OTN Network Port functionality OTN Network Ports (ONP) combine Provider Network Port (PNP) functionality with an OTN physical layer Ethernet MEP and MIP functions Includes support for Y.1731 Ethernet OAM, G.8021 OAM processing and G.8031 APS OAM Ethernet to OTN (de)mapping/(de)muxing functions: Support of the EISS  S-Tag insertion/extraction Support of the ISS by additional technologies  GFP-F/OTN EISS EISS EISS EISS EISS EISS ISS EISS EISS EISS EISS EISS ISS EISS Frame filtering (8.6.3) Supports G.8031 SNC Protection Up MPs (6.17, 19.2, 19.3) Up MPs (6.17, 19.2, 19.3) O T N N E T W O R K P O R T s Port filtering entities (8.6.1/2/4/5) Port filtering entities (8.6.1/2/4/5) Supports Y.1731 OAM Down MPs (6.17, 19.2, 19.3) Down MPs (6.17, 19.2, 19.3) PNP equivalent Linktrace Output Multiplexer (19.5) Linktrace Output Multiplexer (19.5) Queuing entities (8.6.6/7/8) Queuing entities (8.6.6/7/8) S-Tagging Support of the EISS Support of the EISS Support of the ISS by additional technologies (6.15) Support of the ISS by additional technologies (6.15) GFP-F OTN specific OTN ODU Down MP OTN ODU Down MP OTN other functions OTN other functions

  34. ODUk with GFP-F encapsulated S-Tagged Ethernet frames 16 3808 ODUk 4 GFP IDLEs ODUk bit rates 1.25G 2.5G 3.75G 5G 6.25G 7.5G 8.75G 10G 11.25G : : 100G GFP Core Header PLI cHEC GFP Payload Header PTI PFI EXI UPI tHEC PTI=000: Client Data PFI=0: no Payload FCS EXI=000: Null Extension Header UPI=0000 0001: Frame Mapped Ethernet DA DA SA SA S-VLAN Tag TPID = 88-a8 PCP DEI VID TYPE MAC SDU MAC FCS

  35. Transport Bridge Transport Bridge Line Ports S-VLAN Component To/from PEB & PB & IBBEB & MEF E-NNI PNP PNP PNP PNP A ??? To/from IBEB & TBEB & BBEB ??? I-Tagged LANs D OTN ADMs/XCs (P2P ODUs) OTN ADMs/XCs (P2P ODUs) E ONP ONP ONP ONP SDH ADMs/XCs (P2P VCs) SDH ADMs/XCs (P2P VCs) SNP SNP SNP SNP MPLS-TP P nodes (P2P transport-LSPs) MPLS-TP P nodes (P2P transport-LSPs) MTNP MTNP MTNP MTNP

  36. PTN NT Eth UNI PTN NT A N IB-BEB TE M I-Tagged ECs Eth UNI Eth UNI PBB- TEN IB-BEB TE Eth UNI S-Tagged ECs PBBN B-BEB B I-BEB BCB TE B-BEB B-BEB L I-Tagged ECs IB-BEB TE Eth UNI S-Tagged ECs C T-BEB Eth UNI B-BEB BCB OTN S-Tagged ECs I-Tagged ECs Eth UNI Eth UNI TB D PEB TB S-Tagged ECs E TEB PBN PB TB S-Tagged ECs OXC OXC PB TB Eth UNI TEB K PB PB TB S-Tagged ECs OXC OTM-0 with S-Tagged ECs TB PTN NT I-Tagged ECs TB F J TEB TB Eth UNI TB G I-BEB S-Tagged ECs S-Tagged ECs Eth UNI Eth UNI H PEB PTN NT I Eth UNI Eth UNI Transport Network • Option 1 animated

  37. PTN NT Eth UNI PTN NT A N IB-BEB TE M S-Tagged ECs Eth UNI Eth UNI PBB- TEN IB-BEB TE Eth UNI S-Tagged ECs PBN+ PB(BCB) B IB-BEB BCB TE IB-BEB L IB-BEB TE Eth UNI S-Tagged ECs C PB(BCB) Eth UNI PB(BCB) Eth UNI OTN S-Tagged ECs S-Tagged ECs D Eth UNI TB PEB TB S-Tagged ECs E TEB PBN PB TB S-Tagged ECs OXC OXC PB TB Eth UNI TEB K PB PB TB S-Tagged ECs OXC OTM-0 with S-Tagged ECs TB PTN NT S-Tagged ECs TB F J TEB TB Eth UNI TB G IB-BEB S-Tagged ECs S-Tagged ECs Eth UNI Eth UNI H PEB PTN NT I Eth UNI Eth UNI Transport Network • Option 2

  38. PTN NT Eth UNI PTN NT A N IB-BEB TE M S-Tagged ECs Eth UNI Eth UNI PBB- TEN IB-BEB TE Eth UNI S-Tagged ECs PBBN IB-BEB B IB-BEB BCB TE IB-BEB IB-BEB L S-Tagged ECs IB-BEB TE Eth UNI S-Tagged ECs C TB-BEB Eth UNI IB-BEB BCB OTN S-Tagged ECs S-Tagged ECs Eth UNI IB-BEB Eth UNI TB PEB TB S-Tagged ECs D E TEB PBN PB TB S-Tagged ECs OXC OXC PB TB Eth UNI TEB K PB PB TB S-Tagged ECs OXC OTM-0 with S-Tagged ECs TB PTN NT I-Tagged ECs TB F J TEB TB Eth UNI TB G IB-BEB S-Tagged ECs S-Tagged ECs Eth UNI Eth UNI H PEB PTN NT I Eth UNI Eth UNI Transport Network • Option 2

  39. PB/PBB/PBB-TE networkOption 2 implications Additional I-Component to be used as UNI port PEB* PIP CBP PBB/PBB-TE Network A I I-Comp PEB UNI CNP CNP CNP UNI (I)B-BEB (I)B-BEB (I)B-BEB S S CEP PNP CNP UNI BCB BCB PNP S IB-BEB PIP B(I) B(I) B(I) I See slide 29 for B-Tagged LAN frame formats I I-BEB PBB/PBB-TE Network B CNP on I-BEB can not be used as UNI port UNI CBP CBP CBP UNI PBB/PBB-TE Network C Additional IB-BEB to be used as UNI port CNP B(I) UNI CEP CNP CNP I(B)-BEB (I)B-BEB (I)B-BEB S BCB BCB PNP CNP on IB-BEB can not be used as UNI port S UNI IB-BEB B(I) B(I) B(I) I Two IB-BEBs to support bundled S-VLAN service UNI CNP CBP CBP UNI CNP

  40. EVC – EC –B-VLAN/ESP/ODU/…. untagged individual C-VLAN bundled C-VLAN port-based EVC individual S-VLAN none bundled S-VLAN transparent QiQ tpmr encapsulation 1x individual BSI MiM bundled BSI EC QiQ+MiM nx nx nx nx nx S-Tag or I-Tag I-Tag or S-Tag+I-Tag I-Tag S-Tag S-Tag 802.3 B-VLAN ESP ODU VC-n … nx nx nx nx S-Tagged LAN I-Tagged LAN  B-Tag ESP-Tag/ESP-DA/ESP-SA timeslots 802.3 802.3 OTM-n ODU B-Tagged LAN ESP-Tagged LAN

  41. Two PIP flavours traditional I-Tagging PIP and alternative S-Tagging PIP* I-Tagging PIP S-Tagging PIP* difference BSI Multiplex Entity (6.18) EISS Multiplex Entity (6.17)

  42. Two CBP flavours traditional I-to-I Tagging CBP and alternative I-to-S-Tagging CBP* I-to-I-Tagging EC CBP I-to-S-Tagging EC CBP* difference BSI Multiplex Entity (6.18) EISS Multiplex Entity (6.17)

  43. I-Tagged EC  S-Tagged EC Interworking Function principle • One or more c6.17 EISS Multiplex Entity functions may be connected with one BSI Multiplex Entity function as illustrated below to provide an I-Tagged EC to S-Tagged EC interworking function S-VID EISS EISS EISS Multiplex Entity (6.17) EISS Multiplex Entity (6.17) ISS ISS ISS ISS ISS ISS ISS ISS ISS ISS ISS ISS BSI Multiplex Entity (6.18) EISS I-SID I-SID= 0 0 0 0 0 0 0 0 0 0 0 1 S-VID I-SID= 0 0 0 0 0 0 0 0 0 0 1 0 S-VID

More Related