E-OTN status update and
service interface question
[associated with ITU-T liaison statement
liaison-itut-sg15-ols-277-0310]
Maarten Vissers
2011-03-13
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
2
Introduction
3
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 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”, …
4
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
5
Introduction
EOTN
Ethernet Services Layer
an “Ethernet Services layer” which
Transport Services Layer
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)
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)
Management Plane
Application Services Layer
Control Plane
The EOTN includes:
Ordering , Provisioning, Billing,
Management and Support
Data Plane
The EOTN architecture is aligned with
MEF’s Global Interconnect architecture
6
Introduction
EOTN
Transport Edge Bridges (TEB) interconnected via Transport Bridges (TB)
Customer MA
Ethernet
Services
Layer
Provider MA
Operator MA
Operator MA
ENNI
UNI
Transport
Services
Layer
SDH
TEB
ENNI
NNI
OTN
TB
UNI
OTN
OTN
TB
CEX
TB
TB
TB
ETH
TB
TEB
TEBs and TBs interconnected via Transport
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
7
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
8
Ethernet Services in EOTN
9
EPL services supported
in SDH, OTN
Ethernet Services Overview
Frame Based Ethernet Services in EOTN
UNI Link
UnTagged or Priority-Tagged
Ethernet services
UNI Link
Ethernet
service
Ethernet
service
G.8011.x
service
types
EPL Type 2
EPL Type 2/TT
Ethernet
service
Transparent service
Port based service
Two port MAC relay service
EPL Type 1, EVPL Type 2
EPT, EVPT Type 2
EPLAN, EVPLAN Type 2
(V-)UNI
Link
Ethernet
service
Ethernet
service
(V-)UNI
Link
UNI Link
UNI Link
UNI Link
S- + C-Tagged or
B- + I-Tagged
Ethernet services
UNI Link
UNI Link
UNI Link
Bit/CodeWord
stream service
UNI Link
UNI Link
Ethernet
service
Ethernet service
C-Tagged or S-Tagged or
I-Tagged or B-Tagged
Ethernet services
Ethernet
service
Ethernet
service
C-Tagged service
S/B-Tagged service
I-Tagged service
C-Tagged service
I-Tagged service
EVPL Type 1/3
EVPT Type 1/3
EVPLAN Type 1/3
EVPL Type 1/3
EVPT Type 1/3
EVPLAN Type 1/3
Ethernet Services
Ethernet services are supported in the EOTN by its STagged 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-inMAC encapsulation may also be deployed for e.g. mp bundled
C-VLAN services (see “C” in slide 12)
11
Line Ports
S-Tagged LANs
To/from PEB &
PB & IBBEB &
MEF E-NNI
D
SDH ADMs/XCs
(P2P VCs)
CNP
PEP
Port Based Service Interface
(un- C-, priority-S- I-Tagged)
MPLS-TP P nodes
S-Tagged Service Interface
(S-Tagged)
Remote Customers C-Tagged
service interface
?
???
ONP
ONP
CNP
PEP
CNP
PEP
CNP
CNP
C-VLAN
Component CEP
Remote Customer Portbased Service Interface
Remote Customers S-Tagged
Service interface
PAP
Port-based, S- & C-Tagged
Service Interface
(S-, S+C-Tagged)
RCAP
S-VLAN
Component
PAP
A
PNP
I-Tagged service interface
(I-Tagged)
Individual or bundled I-Tagged Services
CBP
?
CNP
PIP
CBP
PIP
B
CNP
PEP C-VLAN
Component CEP
C-Tagged Service Interface
(un-, priority-C-, C-Tagged)
CNP
PEP
Port Based Service Interface
(un-, C-, priority-S- I-Tagged)
CNP
CNP
Remote Customers C-Tagged
service interface
SNP
IComponent CNP
PEP
SNP
CNP
PEP
CNP
(P2P transport-LSPs)
C-Tagged Service Interface
(un-, priority-C-. C-Tagged)
C-VLAN
Component CEP
Individual S-VLAN Service
Interworking
function
(P2P ODUs)
PEP
CNP
???
OTN ADMs/XCs
CNP
CNP
PNP
To/from IBEB &
TBEB & BBEB
Tributary Port functonality
PNP
S-VLAN Component
Ethernet Services support in
Transport Edge Bridge
Transport Edge Bridge
MTNP
CNP
C-VLAN
Component CEP
Remote Customer Portbased Service Interface
Remote Customers S-Tagged
Service interface
S-Tagged Service Interface
(S-Tagged)
PAP
S-VLAN RCAP
Component
PAP
PNP
Port-based , S- & C-Tagged
Service Interface
(S-, S+C-Tagged)
C
MTNP
CNP
TPIP Component CNP
CBP
TPIP Component CNP
?
Transparent Service Interface
(un-, C-, S-, I-Tagged)
Transparent Service Interface
12
(un-, C-, S-, I-Tagged)
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 TBEB or TB-BEB nodes
13
Hybrid EOTN – PBBN EC options
14
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 STagged 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
Customer MA
Ethernet
Services
Layer
EC Provider MA
Operator MA
Operator MA
ENNI
UNI
Transport
Services
Layer
I-Tagged EC segment
OTN
TEB
ENNI
I-LAN
OTN
TB
PBBN
UN
I
OTN
TB
CEX
TB
TB
BBEB
BBEB
IBEB
Interworking function
CEX: Carrier Ethernet Exchange
TEB: Transport Edge Bridge
TB: Transport Bridge
15
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 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
S-Tagged EC
S-Tagged EC segment
Ethernet
Services
Layer
EC Provider MA
Operator MA
Operator MA
ENNI
UNI
Transport
Services
Layer
Customer MA
ENNI
NNI
P(B)BN
IB
BEB
CEX: Carrier Ethernet Exchange
PB
(BCB)
OTN
OTN
PB
(BCB)
CEX
TB
TEB: Transport Edge Bridge
TB
TB
TB: Transport Bridge
OTN
TB
UN
I
TEB
16
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
Ethernet
Services
Layer
EC Provider MA
Operator MA
UNI
Transport
Services
Layer
Customer MA
NNI
Operator MA
ENNI
ENNI
NNI
PBBN
IB
IB
BCB
BEB1 BEB2
CEX: Carrier Ethernet Exchange
OTN
OTN
IB
BEB3
CEX
TB
TEB: Transport Edge Bridge
TB
TB
TB: Transport Bridge
OTN
TB
UN
I
TEB
17
Hybrid EOTN-PBBN EC comparison
Option 1
I-Tagged LANs supported
Requires interworking
function to interconnect STagged EC segment with ITagged EC segment
IW function has to convert ITag 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?
EC endpoints can be in
EOTN TEBs, PBBN I-BEBs,
IB-BEBs, T-BEBs and TBBEBs
Multi domain PBBNs
Option 2
18
EC Frame Format Options
19
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= 0 0 0 0 0 0 0 0 0 0 0 1
VID
20
Option 1 EC Frame Formats
Individual service
B-SA
Type = 89-10
B-SA
TPID = 88-a8
PCP
DEI
B-DA
B-DA
S-VID
Type = 89-10
C-DA
C-DA
C-DA
C-SA
Type
C-SA
Type
C-SA
Type
MSDU
MSDU
MSDU
EC Frame (= BSI Frame)
N+14 octets
S-Tagged EC Frame
N + 18 octets
B-SA
Type = 89-10
B-SA
TPID = 88-E7
PCP
0
Res1
B-DA
B-DA
Res2
I-SID
I-SID
C-DA
C-DA
C-DA
C-SA
Type
C-SA
Type
C-SA
Type
MSDU
MSDU
MSDU
EC Frame (=BSI Frame)
N+14 octets
I-Tagged EC Frame
N+18 octets
EVC Frame
N octets
Frame format
in PBBN
6
6
2
6
6
2
2
2
DEI
EVC Frame
N octets
Frame format
in EOTN
6
6
2
6
6
2
2
2
21
Option 1 EC Frame Formats
S-VID
Type = 89-10
C-DA
C-SA
C-SA
TPID = 81-00 or 88-a8
C-SA
TPID = 81-00 or 88-a8
PCP
X
VID
Type
2
2
PCP
VID
Type
MSDU
MSDU
EC Frame (= BSI Frame)
N+18 octets
S-Tagged EC Frame
N+22 octets
B-SA
Type = 89-10
PCP
0
Res1
B-DA
B-SA
TPID = 88-E7
Res2
I-SID
I-SID
C-DA
C-DA
C-DA
C-SA
C-SA
TPID = 81-00 or 88-a8
C-SA
TPID = 81-00 or 88-a8
VID
Type
X
MSDU
C-/S-Tagged EVC Frame
2
2
PCP
X
TPID = 81-00 or 88-a8
VID
Type
2
2
PCP
X
X
6
6
2
B-DA
VID
Type
Frame format
in PBBN
X: CFI or DEI
6
6
2
2
2
DEI
VID
Type
2
2
C-/S-Tagged EVC Frame
N+4 octets
PCP
PCP
C-DA
MSDU
6
6
2
2
TPID = 88-a8
C-DA
TPID = 81-00 or 88-a8
PCP
B-SA
Type = 89-10
B-SA
X
2
2
B-DA
B-DA
Frame format
in EOTN
6
6
2
6
6
2
2
2
DEI
Bundled C-/S-VLAN service
MSDU
MSDU
EC Frame (=BSI Frame)
I-Tagged EC Frame N+22 octets
22
Option 1 EC OAM Frame Formats
B-SA
TPID = 88-a8
DEI
B-DA
B-DA
Type = 89-02
B-SA
Type = 89-02
OAM PDU
OAM PDU
OAM PDU
EC OAM Frame
M+12 octets
S-Tagged EC OAM Frame
M+16 octets
B-DA
S-VID
Type = 89-02
B-DA = f(B-DA,DBD)
PCP
0
Res1
B-SA
TPID = 88-E7
Res2
I-SID
I-SID = f(ETH_FP)
C-DA = B-DA
Type = 89-02
B-SA
Type = 89-02
OAM PDU
OAM PDU
OAM PDU
EC OAM Frame
M+12 octets
I-Tagged EC OAM Frame
M+30 octets
OAM PDU
M octets
C-SA = B-SA
Type = 89-02
Frame format
in PBBN
6
6
6
6
2
2
2
6
6
DEI
OAM PDU
M octets
PCP
Frame format
in EOTN
6
6
6
6
2
2
23
B-DA
B-SA
TPID = 88-a8
DEI
B-DA
6
6
6
6
2
2
Type = 89-02
B-SA
Type = 89-02
OAM PDU
OAM PDU
OAM PDU
EC OAM Frame
M+12 octets
S-Tagged EC OAM Frame
M+16 octets
0
Res2
I-SID
I-SID = fixed value
B-SA
TPID = 88-a8
PCP
PCP
S-VID
TPID = 88-E7
0
Res1
PCP
Res1
B-SA
TPID = 88-E7
S-VID
Type = 89-02
B-DA
DEI
B-DA
DEI
6
6
2
2
2
6
6
2
2
2
2
2
DEI
OAM PDU
M octets
PCP
Res2
I-SID
I-SID = fixed value
C-DA
C-DA
C-DA
C-SA
Type
C-SA
Type
C-SA
Type
MSDU
MSDU
MSDU
EC Frame (= B-VLAN Frame)
N+18 octets
S-Tagged EC Frame
N+22 octets
EVC Frame
N octets
Frame format in Frame format in
EOTN & PBBN
EOTN & PBBN
Option 2 EC & EC OAM Frame Formats
Individual service
24
C-SA
Res2
I-SID = e.g. 4096 + VID
S-VID
TPID = 88-E7
0
Res2
Type
C-SA
Type
C-SA
Type
MSDU
MSDU
MSDU
PCP
0
Res1
B-SA
TPID = 88-E7
Res2
I-SID
I-SID = fixed value
Res1
B-DA
DEI
6
6
2
2
2
S-Tagged EC Frame (N+22 octets)
B-DA
6
B-SA
6
TPID = 88-a8
2
S-VID
2 PCP
TPID = 88-E7
2
I-SID
2 PCP 0 Res2
I-SID = fixed value
2
DEI
EC Frame (= B-VLAN Frame)
N+18 octets
DEI
VID
C-DA
C-DA
C-DA
C-SA
C-SA
C-SA
TPID
VID
X
Type
MSDU
C-/S-Tagged EVC Frame
2
2
TPID
PCP
X
TPID
VID
Type
I-SID
I-SID = e.g. 4096 + VID
C-DA
2A
PCP
PCP
2
2
PCP
X
PCP
I-SID
PCP
Res1
0
TPID = 88-a8
DEI
PCP
B-SA
C-DA
C-/S-Tagged EVC Frame
N+4 octets
2
2
TPID = 88-E7
TPID
X
2
2
B-SA
Res1
C-DA
B-DA
DEI
2B
6
6
2
2
2
B-DA
DEI
Bundled C-/S-VLAN service
6
6
2
2
2
2
2
Frame format in Frame format in
EOTN & PBBN
EOTN & PBBN
Option 2 EC Frame Formats
VID
Type
MSDU
MSDU
EC Frame (= B-VLAN Frame)
S-Tagged EC Frame (N+26 octets)
25
S-Tagged EC Frame format in EOTN
comparison - Individual service
Option 2
TPID = 88-a8
PCP
S-VID
Type = 89-10
B-SA
TPID = 88-a8
PCP
PCP
S-VID
TPID = 88-E7
0
Res1
B-SA
B-DA
DEI
B-DA
DEI
6
6
2
2
2
6
6
2
2
2
2
2
DEI
Option 1
Res2
I-SID = fixed value
C-DA
C-DA
C-SA
Type
C-SA
Type
MSDU
MSDU
S-Tagged EC Frame
N + 18 octets
Difference
4 octets
I-SID
S-Tagged EC Frame
N+22 octets
Difference in frame formats
is in the red boxes
26
S-Tagged EC Frame format in EOTN
comparison - Bundled C-/S-VLAN service
Option 2A
0
Res1
PCP
DEI
TPID = 88-E7
Res2
TPID = 88-a8
PCP
Type = 89-10
I-SID
I-SID = e.g. 4096 + VID
C-DA
2
2
C-SA
Type
S-VID
TPID = 88-a8
PCP
PCP
S-VID
TPID = 88-E7
0
Res1
S-VID
B-SA
Res2
C-DA
C-SA
TPID = 81-00 or 88-a8
C-SA
TPID
PCP
VID
2
2
PCP
VID
Type
Type
MSDU
MSDU
S-Tagged EC Frame
N+22 octets
Difference
0 octets
S-Tagged EC Frame
N + 22 octets
I-SID
I-SID = fixed value
C-DA
X
PCP
DEI
B-SA
TPID = 88-a8
B-DA
B-SA
DEI
6
6
2
2
2
DEI
B-DA
B-DA
X
6
6
2
2
2
2
2
6
6
2
2
2
2
2
DEI
Option 1
Option 2B
MSDU
Difference
4 octets
S-Tagged EC Frame
N+26 octets
Difference in frame formats is in
the red and green boxes
27
PBBN B-Tagged LAN Frame Formats
28
PBB network
Option 1 frame format
Res1
EC BSI I-Tag
EVC encaps I-Tag
DEI
PBBN B-VLAN B-Tag
DEI
EC’s B-DA/SA
PBBN B-Tagged LAN
Frame Format
B-DA
6
B-SA
6
TPID = 88-a8
2
B-VID
2 PCP
TPID
=
88-E7
2
I-SID
2 PCP 0 Res2
I-SID
2
C-DA
EVC Frame
C-SA
Type
MSDU
B(I)-Tagged EC Frame
N+22 octets
Option 1 frame format on
a B-Tagged LAN is the
regular 802.1ah frame
format with
One
One
One
One
B-DA
B-SA
B-Tag
I-Tag
PBB network
Option 2 – frame formats
IB-BEB2 PIP inserts
S-Tag and I-Tag
EVC Frame
EVC encaps I-Tag
DEI
Res1
EC’s B-DA/SA
Res1
PBBN EC I-Tag
DEI
Res1
DEI
DEI
PBBN B-VLAN B-Tag
C-DA
C-DA
C-SA
Type
C-SA
Type
MSDU
MSDU
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
IB-BEB1
EVC encaps I-Tag
PBBN B-DA/SA
DEI
EC’s S-Tag
Res1
EC’s B-DA/SA
DEI
PBBN BSI I-Tag
DEI
PBBN B-VLAN B-Tag
PBBN B-Tagged LAN
Frame Format
B-DA
6
B-SA
6
TPID = 88-a8
2
PCP
B-VID
2
TPID = 88-E7
2
I-SID
2 PCP 0 Res2
I-SID
2
B-DA
6
B-SA
6
TPID = 88-E7
2
I-SID
2 PCP 0 Res2
I-SID = fixed value
2
IB-BEB2
PBBN B-DA/SA
PBBN B-Tagged LAN
Frame Format
B-DA
6
B-SA
6
TPID = 88-a8
2
B-VID
2 PCP
TPID = 88-E7
2
I-SID
2 PCP 0 Res2
I-SID
2
B-DA
6
B-SA
6
TPID = 88-a8
2
S-VID
2 PCP
TPID
=
88-E7
2
I-SID
2 PCP 0 Res2
I-SID = fixed value
2
IB-BEB2 PIP
inserts I-Tag only
What is the best option?
Option 1?
If option 1, then who should describe the I-Tagged EC to STagged 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 SVLAN and transparent EVCs?
31
Annex
32
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)
EISS
Up MPs (6.17, 19.2, 19.3)
EISS
Port filtering entities (8.6.1/2/4/5)
EISS
PNP
equivalent
Down MPs (6.17, 19.2, 19.3)
EISS
Linktrace Output Multiplexer (19.5)
EISS
Queuing entities (8.6.6/7/8)
EISS
Support of the EISS
ISS
Support of the ISS by additional
technologies (6.15)
OTN
specific
OTN ODU Down MP
OTN other functions
EISS
O
T
N
N
E
T
W
O
R
K
P
O
R
T
s
Up MPs (6.17, 19.2, 19.3)
EISS
Port filtering entities (8.6.1/2/4/5)
EISS
Down MPs (6.17, 19.2, 19.3)
EISS
Supports
G.8031 SNC
Protection
Supports
Y.1731 OAM
Linktrace Output Multiplexer (19.5)
EISS
Queuing entities (8.6.6/7/8)
EISS
Support of the EISS
ISS
Support of the ISS by additional
technologies (6.15)
S-Tagging
GFP-F
OTN ODU Down MP
OTN other functions
33
ODUk with GFP-F encapsulated
S-Tagged Ethernet frames
16
3808
O
D
U
k
GFP IDLEs
PTI
PFI
PLI
EXI
cHEC
tHEC
UPI
DA
DA
SA
TPID = 88-a8
TYPE
SA
PCP
DEI
ODUk
bit rates
1.25G
2.5G
3.75G
5G
6.25G
7.5G
8.75G
10G
11.25G
:
:
100G
4
MAC SDU
MAC FCS
VID
GFP Core Header
GFP Payload Header
PTI=000:
Client Data
PFI=0:
no Payload FCS
EXI=000:
Null Extension Header
UPI=0000 0001: Frame Mapped Ethernet
S-VLAN Tag
Transport Bridge
Transport Bridge
Line Ports
(P2P ODUs)
SDH ADMs/XCs
(P2P VCs)
MPLS-TP P nodes
(P2P transport-LSPs)
PNP
PNP
PNP
ONP
ONP
S-VLAN Component
OTN ADMs/XCs
PNP
To/from PEB &
PB & IBBEB &
MEF E-NNI
???
To/from IBEB &
TBEB & BBEB
???
I-Tagged LANs
ONP
OTN ADMs/XCs
(P2P ODUs)
ONP
SNP
SNP
SNP
SNP
MTNP
MTNP
MTNP
MTNP
SDH ADMs/XCs
(P2P VCs)
MPLS-TP P nodes
(P2P transport-LSPs)
35
PTN
NT I-Tagged ECs
Eth UNI
Eth UNI
Eth UNI
B
Eth UNI
C
B-BEB
BCB
Eth UNI
Eth UNI
PEB
E
D
S-Tagged
S-Tagged
ECs
B-BEB
I-Tagged
ECs
Eth UNI
Transport
Network
TB
S-Tagged
ECs
S-Tagged ECs
PB
Eth UNI
K
TB
OXC
I-Tagged
ECs
G
I-BEB
TB
TB
TB
TB
S-Tagged ECs
Option 1
H
Eth UNI
PEB
OTM-0 with
S-Tagged ECs
TEB
S-Tagged
ECs
Eth UNI
animated
TEB
OXC
OTN
OXC
TB
PB
PTN
NT
Eth UNI
L
IB-BEB
TE
TB
S-Tagged
ECs
F
PBBTEN
M
TB
PB
PB
IB-BEB
TE
BCB
TE
ECs
PBN
IB-BEB
TE
PBBN
B-BEB
T-BEB
S-Tagged ECs
B-BEB
I-BEB
I-Tagged
ECs
Eth UNI
PTN
NT
N
TEB
A
J
Eth UNI
PTN
NT
I
Eth UNI
36
PTN
NT S-Tagged
Eth UNI
ECs
A
Eth UNI
Eth UNI
S-Tagged ECs
PB
(BCB)
IB-BEB
IB-BEB
TE
C
PB
(BCB)
IB-BEB
Eth UNI
Eth UNI
PEB
E
S-Tagged
ECs
PB
(BCB)
S-Tagged
ECs
D
PBN
Eth UNI
Transport
Network
TB
S-Tagged
ECs
TB
PB
S-Tagged ECs
PB
Eth UNI
K
TB
OXC
S-Tagged
ECs
PTN
NT
G
TB
TB
TB
TB
IB-BEB
S-Tagged ECs
Option 2
H
Eth UNI
PEB
OTM-0 with
S-Tagged ECs
TEB
S-Tagged
ECs
Eth UNI
animated
TEB
OXC
OTN
OXC
S-Tagged
ECs
Eth UNI
L
IB-BEB
TE
TB
PB
F
M
TB
S-Tagged
ECs
PB
PBBTEN
BCB
TE
PBN+
Eth UNI
IB-BEB
TE
TEB
B
Eth UNI
PTN
NT
N
J
Eth UNI
PTN
NT
I
Eth UNI
37
PTN
NT S-Tagged
Eth UNI
ECs
A
Eth UNI
Eth UNI
S-Tagged ECs
IB-BEB
IB-BEB
S-Tagged
ECs
Eth UNI
C
IB-BEB
Eth UNI
IB-BEB
PEB
E
BCB
S-Tagged
ECs
Eth UNI
S-Tagged
ECs
Eth UNI
Transport
Network
TB
TEB
OXC
OTN
OXC
TB
PB
S-Tagged ECs
PB
Eth UNI
K
TB
OXC
I-Tagged
ECs
PTN
NT
G
TB
TB
TB
TB
IB-BEB
S-Tagged ECs
Option 2
H
Eth UNI
PEB
OTM-0 with
S-Tagged ECs
TEB
S-Tagged
ECs
Eth UNI
animated
L
IB-BEB
TE
TB
S-Tagged
ECs
Eth UNI
M
TB
S-Tagged
ECs
PBN
PB
S-Tagged
ECs
IB-BEB
D
PB
PBBTEN
BCB
TE
PBBN
IB-BEB
TB-BEB
F
IB-BEB
TE
IB-BEB
TE
TEB
B
Eth UNI
PTN
NT
N
J
Eth UNI
PTN
NT
I
Eth UNI
38
PB/PBB/PBB-TE network
Option 2 implications
Additional IComponent to be
used as UNI port
I
B(I)
B(I)
CBP
S
I
CBP
CBP
PBB/PBB-TE
Network B
CNP on I-BEB
can not be used CNP
as UNI port
UNI
CNP
UNI CNP
CNP on IB-BEB
can not be used
as UNI port
S
I
CBP
B(I)
BCB
B(I)
B(I)
See slide 29 for
B-Tagged LAN
frame formats
CNP
(I)B-BEB
B(I)
CNP
(I)B-BEB
S UNI
BCB
IB-BEB
PNP
PBB/PBB-TE
Network C
UNI CEP
I(B)-BEB
Additional IBBEB to be used
as UNI port
B(I)
BCB
PIP
CNP
(I)B-BEB
S
CNP
(I)B-BEB
PNP
S
UNI
PBB/PBB-TE
Network A
CNP
BCB
IB-BEB
UNI
PNP
UNI CEP
I-BEB
CNP
PEB
UNI
I-Comp
UNI
CBP
I
(I)B-BEB
PIP
PEB*
CBP
Two IB-BEBs to
support bundled SVLAN service
39