1. E-OTN status update and service interface question [associated with ITU-T liaison statement liaison-itut-sg15-ols ] version 01
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)
Maarten Vissers

2. Contents Introduction Ethernet Services in EOTN
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. Introduction G.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 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. Introduction EOTN
Data Plane
Control Plane
Management Plane
Transport Services Layer
Ethernet Services Layer
Application Services Layer
Ordering , Provisioning, Billing, Management and Support
The EOTN architecture is aligned with MEF’s Global Interconnect architecture
The EOTN includes:
an “Ethernet Services layer” which provides for S-Tagged ECs; each EC carries 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)

7. Introduction EOTN
Transport Edge Bridges (TEB) interconnected via Transport Bridges (TB)
Customer MA
Ethernet Services Layer
Provider MA
Operator MA
Operator MA
UNI
TEBs and TBs interconnected via Transport
UNI
Transport Services Layer
SDH
OTN
OTN
NNI
OTN
ETH
ENNI
ENNI
TEB TB TB
CEX TB TB TB TB
TEB
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.
TB/TEBs may also contain other types of transport network ports; e.g. SDH, MPLS-TP, … This is not further addressed in this presentation
CEX: Carrier Ethernet Exchange TEB: Transport Edge Bridge TB: Transport Bridge

8. Introduction EOTN 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
UNI Link
UNI Link
UNI Link
(V-)UNI Link
Ethernet service
Ethernet service
Ethernet service
UNI Link
UNI Link
UNI Link
(V-)UNI Link
Ethernet service
Ethernet service
Ethernet service
Ethernet service
Bit/CodeWord stream 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
G.8011.x service types
EPL Type 2 EPL Type 2/TT
EPL Type 1, EVPL Type 2 EPT, EVPT Type 2 EPLAN, EVPLAN Type 2
EVPL Type 1/3 EVPT Type 1/3 EVPLAN Type 1/3
EVPL Type 1/3 EVPT Type 1/3 EVPLAN 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. Ethernet Services support in Transport Edge Bridge
S-Tagged LANs
S-VLAN Component
S-VLAN
Component
C-VLAN
Transport Edge Bridge
CEP
PAP
PEP
CNP
RCAP
PNP
ONP
Remote Customers S-Tagged Service interface T-
CBP
I-Tagged service interface
(I-Tagged) I-
PIP
S-Tagged Service Interface
(S-Tagged)
C-Tagged Service Interface
(un-, priority-C-. C-Tagged)
Port Based Service Interface
(un- C-, priority-S- I-Tagged)
Transparent Service Interface
(un-, C-, S-, I-Tagged)
Port-based, S- & C-Tagged Service Interface
(S-, S+C-Tagged)
(un-, priority-C-, C-Tagged)
(un-, C-, priority-S- I-Tagged)
Individual or bundled I-Tagged Services
Individual S-VLAN Service
Remote Customer Port-based Service Interface
Remote Customers C-Tagged service interface
Port-based , S- & C-Tagged Service Interface
???
Tributary Port functonality
Line Ports
SNP
MTNP ?
To/from PEB & PB & IBBEB & MEF E-NNI
To/from IBEB & TBEB & BBEB D A
Ethernet Services support in Transport Edge Bridge
Interworking function B
OTN ADMs/XCs
(P2P ODUs)
SDH ADMs/XCs
(P2P VCs)
A: traditional PEB functionality
B: I-Tagged service interface (re-used from I-BEB)
C: (bundled) S-VLAN service, (bundled) C-VLAN service and transparent service interfaces (re-used from IB-BEB and TB-BEB); specific encapsulation is to be decided… subject of this presentation
D: NNI ports to connect with I-BEB, T-BEB, B-BEB (via I-Tagged LAN); specific functionality is to be decided… subject of this presentation
E: transport NNI ports, e.g. OTN Network Port (ONP); see annex for detailed model C
MPLS-TP P nodes
(P2P transport-LSPs) E

13. MAC-in-MAC encapsulated Ethernet 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)
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)
S-Tagged EC segment
I-Tagged EC segment
Customer MA
Ethernet Services Layer
EC Provider MA
Operator MA
Operator MA
UNI
PBBN
UNI
Transport Services Layer
OTN
OTN
OTN
I-LAN
ENNI
ENNI
TEB TB TB
CEX TB TB
BBEB
BBEB
IBEB
Interworking function
CEX: Carrier Ethernet Exchange TEB: Transport Edge Bridge TB: Transport Bridge

16. Hybrid EOTN-PBBN EC (option 2)
An alternative option to establish a hybrid PBBN-EOTN EC would be to deploy a Backbone VLAN as a “Service VLAN”
Suggested in 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
S-Tagged EC
S-Tagged EC segment
Customer MA
Ethernet Services Layer
EC Provider MA
Operator MA
Operator MA
UNI
P(B)BN
UNI
Transport Services Layer
OTN
NNI
OTN
OTN
ENNI
ENNI IB
BEB
PB (BCB)
PB (BCB)
CEX TB TB TB TB
TEB
CEX: Carrier Ethernet Exchange TEB: Transport Edge Bridge TB: Transport Bridge

17. Hybrid EOTN-PBBN EC (option 2)
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
Two IB-BEBs
S-Tagged EC
S-Tagged EC segment
Customer MA
Ethernet Services Layer
EC Provider MA
Operator MA
Operator MA
UNI
NNI
PBBN
UNI
Transport Services Layer
OTN
NNI
OTN
OTN
ENNI
ENNI IB
BEB1 IB
BEB2
BCB IB
BEB3
CEX TB TB TB TB
TEB
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 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
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
Acceptable for PB/PBBN?

19. EC Frame Format Options

20. Option 1 and 2 EC Frame Formats
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
I-SID= 1
VID

21. Option 1 EC Frame Formats Individual service6
B-DA 6
B-SA 6
B-DA 2
TPID = 88-a8 6
B-SA 2
PCP
DEI
S-VID
Frame format in EOTN 2
Type = 89-10 2
Type = 89-10
C-DA
C-DA
C-DA
C-SA
C-SA
C-SA
MSDU
Type
MSDU
Type
MSDU
Type
EVC Frame
N octets
EC Frame (= BSI Frame)
N+14 octets
S-Tagged EC Frame
N + 18 octets 6
B-DA 6
B-SA 6
B-DA 2
TPID = 88-E7 6
B-SA 2
PCP
DEI
Res1
Res2
I-SID
Frame format in PBBN 2
Type = 89-10 2
I-SID
C-DA
C-DA
C-DA
C-SA
C-SA
C-SA
Type
MSDU
MSDU
Type
MSDU
Type
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 service6
B-DA 6
B-SA 6
B-DA 2
TPID = 88-a8 6
B-SA 2
PCP
DEI
S-VID 2
Type = 89-10 2
Type = 89-10
Frame format in EOTN
C-DA
C-DA
C-DA
C-SA
C-SA
C-SA 2
TPID = or 88-a8 2
TPID = or 88-a8 2
TPID = or 88-a8 2
PCP X
VID 2
PCP X
VID 2
PCP X
VID
Type
MSDU
MSDU
Type
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 6
B-DA 2
TPID = 88-E7 6
B-SA 2
PCP
DEI
Res1
Res2
I-SID 2
Type = 89-10 2
I-SID
Frame format in PBBN 6
C-DA
C-DA
C-DA 6
C-SA
C-SA
C-SA 2
TPID = or 88-a8 2
TPID = or 88-a8 2
TPID = or 88-a8 2
PCP X
VID 2
PCP X
VID 2
PCP X
VID
Type
MSDU
MSDU
Type
MSDU
Type
C-/S-Tagged EVC Frame
EC Frame (=BSI Frame)
I-Tagged EC Frame N+22 octets

23. Option 1 EC OAM Frame Formats6
B-DA 6
B-SA
Frame format in EOTN 6
B-DA 2
TPID = 88-a8 6
B-SA 2
PCP
DEI
S-VID
Type = 89-02
OAM PDU
OAM PDU
Type = 89-02
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 = f(B-DA,DBD) 6
B-SA 2
TPID = 88-E7 2
PCP
DEI
Res1
Res2
I-SID 2
I-SID = f(ETH_FP)
Frame format in PBBN 6
B-DA 6
C-DA = B-DA 6
B-SA 6
C-SA = B-SA
Type = 89-02
OAM PDU
OAM PDU
Type = 89-02
OAM PDU
Type = 89-02
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 Formats Individual service6
B-DA 6
B-SA 6
B-DA 2
TPID = 88-a8
Frame format in EOTN & PBBN 6
B-SA 2
PCP
DEI
S-VID
OAM PDU
Type = 89-02
OAM PDU
Type = 89-02
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 6
B-DA 2
TPID = 88-a8 6
B-SA 2
PCP
DEI
S-VID 2
TPID = 88-E7 2
TPID = 88-E7 2
PCP
DEI
Res1
Res2
I-SID 2
PCP
DEI
Res1
Res2
I-SID
Frame format in EOTN & PBBN 2
I-SID = fixed value 2
I-SID = fixed value
C-DA
C-DA
C-DA
C-SA
C-SA
C-SA
Type
MSDU
MSDU
Type
MSDU
Type
EVC Frame
N octets
EC Frame (= B-VLAN Frame)
N+18 octets
S-Tagged EC Frame
N+22 octets

25. Option 2 EC Frame Formats Bundled C-/S-VLAN service6
B-DA 6
B-SA 2B 6
B-DA 2
TPID = 88-a8 6
B-SA 2
PCP
DEI
S-VID 2
TPID = 88-E7 2
TPID = 88-E7
C-DA 2
PCP
DEI
Res1
Res2
I-SID 2
PCP
DEI
Res1
Res2
I-SID
Frame format in EOTN & PBBN
C-SA 2
I-SID = e.g VID 2
I-SID = e.g VID 2
TPID
C-DA
C-DA 2
PCP X
VID
C-SA
C-SA
Type
MSDU
MSDU
Type
MSDU
Type
C-/S-Tagged EVC Frame
N+4 octets
EC Frame (= B-VLAN Frame)
N+18 octets
S-Tagged EC Frame (N+22 octets) 6
B-DA 6
B-SA 6
B-DA 2
TPID = 88-a8 6
B-SA 2
PCP
DEI
S-VID 2A 2
TPID = 88-E7 2
TPID = 88-E7 2
PCP
DEI
Res1
Res2
I-SID 2
PCP
DEI
Res1
Res2
I-SID
Frame format in EOTN & PBBN 2
I-SID = fixed value 2
I-SID = fixed value
C-DA
C-DA
C-DA
C-SA
C-SA
C-SA 2
TPID 2
TPID 2
TPID 2
PCP X
VID 2
PCP X
VID 2
PCP X
VID
Type
MSDU
MSDU
Type
MSDU
Type
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 6
B-DA 2
TPID = 88-a8 6
B-SA 2
PCP
DEI
S-VID 2
TPID = 88-a8 2
TPID = 88-E7 2
PCP
DEI
S-VID 2
PCP
DEI
Res1
Res2
I-SID 2
Type = 89-10 2
I-SID = fixed value
C-DA
C-DA
C-SA
C-SA
MSDU
Type
MSDU
Type
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. Difference in frame formats is in the red and green boxes
S-Tagged EC Frame format in EOTN comparison - Bundled C-/S-VLAN service
Option 2A
Option 1
Option 2B 6
B-DA 6
B-SA 6
B-DA 6
B-DA 2
TPID = 88-a8 6
B-SA 6
B-SA 2
PCP
DEI
S-VID 2
TPID = 88-a8 2
TPID = 88-a8 2
TPID = 88-E7 2
PCP
DEI
S-VID 2
PCP
DEI
S-VID 2
PCP
DEI
Res1
Res2
I-SID 2
TPID = 88-E7 2
Type = 89-10 2
I-SID = fixed value 2
PCP
DEI
Res1
Res2
I-SID
C-DA
C-DA 2
I-SID = e.g VID
C-SA
C-SA
C-DA 2
TPID = or 88-a8 2
TPID
C-SA 2
PCP X
VID 2
PCP X
VID
MSDU
Type
MSDU
Type
MSDU
Type
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 network Option 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
EC’s B-DA/SA
B-DA 6
B-SA 2
PBBN B-VLAN B-Tag
TPID = 88-a8 2
PCP
DEI
B-VID 2
TPID = 88-E7
EC BSI I-Tag
EVC encaps I-Tag 2
PCP
DEI
Res1
Res2
I-SID 2
I-SID
C-DA
C-SA
EVC Frame
MSDU
Type
B(I)-Tagged EC Frame
N+22 octets

30. PBB network Option 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
PBBN B-Tagged LAN
Frame Format
IB-BEB2 6
PBBN B-DA/SA
B-DA 6
B-SA 2 6
B-DA
PBBN B-VLAN B-Tag
TPID = 88-a8
PBBN B-DA/SA 2
PCP
DEI
B-VID 6
B-SA 2
TPID = 88-E7 2
PBBN B-VLAN B-Tag
TPID = 88-a8
PBBN BSI I-Tag 2
PCP
DEI
Res1
Res2
I-SID 2
PCP
DEI
B-VID 2
I-SID 2
TPID = 88-E7
PBBN EC I-Tag 6
B-DA 2
PCP
DEI
Res1
Res2
I-SID
EC’s B-DA/SA 6
B-SA 2
I-SID 2
TPID = 88-a8 6
B-DA
EC’s S-Tag
EC’s B-DA/SA 2
PCP
DEI
S-VID 6
B-SA 2
TPID = 88-E7 2
TPID = 88-E7
IB-BEB1
EVC encaps I-Tag 2
PCP
DEI
Res1
Res2
I-SID
EVC encaps I-Tag 2
PCP
DEI
Res1
Res2
I-SID 2
I-SID = fixed value 2
I-SID = fixed value
C-DA
C-DA
C-SA
C-SA
EVC Frame
MSDU
Type
MSDU
Type
B(I(S))-Tagged EC Frame
N+44 octets
B(I)-Tagged EC Frame
N+40 octets
Difference with Option 1 is 22 octets
Difference with Option 1 is 18 octets

31. What is the best option? Option 1? Option 2?
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?
Option 1:
Supports EC endpoints on all PBBN components, including I-BEB and T-BEB; supports I-Tagged EC signals outside B-VLAN (i.e. on I-Tagged LAN)
Option 2:
Supports EC endpoints on subset of PBBN components; EC endpoints on I-/T-BEB are not supported; no support of I-Tagged EC outside B-VLAN;
Additional IB/TB-BEB nodes are necessary at edge (see slide 16) to support (bundled) S-VLAN and transparent EVCs; bundled S-VLAN and transparent EVCs will have two I-Tags and two sets of B-DA/SA on a B-Tagged LAN inside a PBBN (see slide 29)

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
Frame filtering (8.6.3)
Supports G.8031 SNC Protection
EISS
EISS
Up MPs (6.17, 19.2, 19.3) O T N E W R K P s
Up MPs (6.17, 19.2, 19.3)
EISS
EISS
Port filtering entities (8.6.1/2/4/5)
Port filtering entities (8.6.1/2/4/5)
Supports Y.1731 OAM
EISS
EISS
Down MPs (6.17, 19.2, 19.3)
Down MPs (6.17, 19.2, 19.3)
EISS
EISS
PNP
equivalent
Linktrace Output Multiplexer (19.5)
Linktrace Output Multiplexer (19.5)
EISS
EISS
Queuing entities (8.6.6/7/8)
Queuing entities (8.6.6/7/8)
EISS
EISS
S-Tagging
Support of the EISS
Support of the EISS
ISS
ISS
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 frames16
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
PLI
cHEC
GFP Core Header
PTI
PFI
EXI
UPI
tHEC
GFP Payload Header
PTI=000: Client Data
PFI=0: no Payload FCS
EXI=000: Null Extension Header
UPI= : Frame Mapped Ethernet DA DA SA SA
TPID = 88-a8
PCP
DEI
VID
S-VLAN Tag
TYPE
MAC SDU
MAC FCS

35. A D E Transport Bridge Transport Bridge S-VLAN Component Line Ports
ONP
PNP
SNP
MTNP
???
I-Tagged LANs
To/from PEB & PB & IBBEB & MEF E-NNI
To/from IBEB & TBEB & BBEB A D E
MPLS-TP P nodes
(P2P transport-LSPs)
SDH ADMs/XCs
(P2P VCs)
OTN ADMs/XCs
(P2P ODUs)
MPLS-TP P nodes
(P2P transport-LSPs)
SDH ADMs/XCs
(P2P VCs)
OTN ADMs/XCs
(P2P ODUs)
A: traditional PB functionality
D: NNI ports to connect with I-BEB, T-BEB, B-BEB (via I-Tagged LAN); specific functionality is to be decided… subject of this presentation
E: transport NNI ports, e.g. OTN Network Port (ONP); see annex for detailed model

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

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

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

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

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
QiQ+MiM EC 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. BSI Multiplex Entity (6.18) EISS Multiplex Entity (6.17)
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. BSI Multiplex Entity (6.18) EISS Multiplex Entity (6.17)
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= 1
S-VID
I-SID= 1
S-VID