DRNI Data Plane Model I/II Comparison
& MAC Address Values in DRNI
Maarten Vissers
2011-10-18
v00
1
Contents
 Introduction
 DRNI Data Plane Models I/II for PB, PBB(-TE) IB-BEB and EOTN TB Portals
 EC MEP/MIP configuration examples in Model I Portal
 EC MEP/MIP configuration examples in Model II Portal
 Comparison between Models I and II
 Generic DRNI Data Plane Model
 MAC address considerations
 EUI48 values
 Model I
– EC ENNI Maintenance Associations
– EC Network Operator Maintenance Associations
– MAC address considerations
 Model II
– EC Network Operator Maintenance Associations
– EC ENNI Maintenance Associations
 Comparison of Models I and II
 Conclusion
2
Introduction
The following slides focus on the DRNI functionality and associated MAC
addresses in the portal nodes of a DRNI protected Ethernet ENNI; the slides
are a follow up of axbq-vissers-drni-and-distributed-protection-examples-a3-0911-v01.pptx
The carrier network specific functionality has been removed; it will be
addressed in a separate document
The simplest DRNI configuration is assumed, including two nodes in a portal,
with one ENNI Link per node and an intra-DAS (virtual) link between the two
nodes in the portal
A portal supports DRNI protected ECs and unprotected ECs (as per MEF
requirement); unprotected ECs are considered to be outside DRNI control
Two data plane models I and II for PB, PBB IB-BEB, PBB-TE IB-BEB and
EOTN TB portals are presented and compared from a MEP/MIP deployment
MAC address requirement is investigated to understand which functions
must use the ENNI or Intra-DAS link port’s EUI48 values, which functions may
use these values and which functions must not use these values
3
PB Portal DRNI Data Plane Model
4
PB Portal DRNI Data Plane Model
S-Relay
EC NO
MEP
EC SP/ENNI
MIP
EC ENNI
MEP
ENNI
Link MEP
S-Relay
Half-DAS
19.2/3/5
Half-DAS
19.2/3/5
EC NO/ENNI MIP
19.2/3/5
19.2/3/5
Link end points
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
8.5
8.5
19.2
19.2
19.2
19.2
6.7
6.7
6.7
6.7
802.3
802.3
802.3
802.3
Link MEP
E-NNI
Link 1
E-NNI
Link 2
Intra-DAS Link
There are two models to configure the EC’s MEP and MIP functions in the data plane (see next slides):
Model I) Unprotected ECs and DRNI protected ECs:
- NO MEP, SP MIP and ENNI MEP on ENNI Link Ports
- NO MIP on Intra-DAS Link Ports
Model II) Unprotected ECs:
- NO MEP, SP MIP and ENNI MEP on ENNI Link Ports
DRNI protected ECs:
- NO MEP, SP MIP and ENNI MEP on Active Gateway’s ENNI or Intra-DAS Link Port
- ENNI MIP on Standby Gateway’s ENNI and Intra-DAS Link Ports
NO: Network Operator, SP: Service Provider
5
PB Portal DRNI Data Plane Model I
All ECs: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
S-Relay
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
ENNI
Link MEP
S-Relay
Half-DAS
Half-DAS
19.2/3/5
19.2/3/5
19.2/3/5
19.2/3/5
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
8.5
8.5
19.2
19.2
19.2
19.2
6.7
6.7
6.7
6.7
802.3
802.3
802.3
802.3
EC NO MIP
EC NO MIP
Link MEP
Link MEP
E-NNI
Link 1
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
ENNI Link
MEP
E-NNI
Link 2
Intra-DAS Link
Protected EC
Unprotected EC
#1 Protected EC
#3
Unprotected EC
#4
#2
Protected EC #1 has its NO MEP, SP MIP and
ENNI MEP functions on the ENNI Link 2 Port.
In addition EC NO MIP functions are present
on the left/right Intra-DAS Ports.
Unprotected EC #4 has its NO MEP, SP MIP
and ENNI MEP functions on ENNI Link 1 Port.
NO: Network Operator, SP: Service Provider
Protected EC #2’s has its NO MEP, SP MIP
and ENNI MEP functions on the ENNI Link 2
Port.
Unprotected EC #3 has its NO MEP, SP MIP
and ENNI MEP functions on ENNI Link 2 Port.
See also backup slides
6
PB Portal DRNI Data Plane Model II
Protected EC: NO MEP, EC SP MIP, EC ENNI MEP on Active Gateway
Unprotected EC: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
S-Relay
S-Relay
Half-DAS
Half-DAS
EC NO MEP
19.2/3/5
19.2/3/5
EC SP MIP
EC ENNI MIP
19.2/3/5
19.2/3/5
EC ENNI MEP
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
8.5
8.5
19.2
19.2
19.2
19.2
6.7
6.7
6.7
6.7
802.3
802.3
802.3
802.3
Link MEP
Link MEP
E-NNI
Link 1
EC NO
MEP
EC SP/ENNI
MIP
EC ENNI
MEP
ENNI Link
MEP
E-NNI
Link 2
Intra-DAS Link
Protected EC
Unprotected EC
#1 Protected EC
#3
Unprotected EC
#4
#2
Protected EC #1’s active GW is left, and its NO
MEP, SP MIP and ENNI MEP functions are on
its Intra-Das Port. In addition EC ENNI MIP
functions are present on the Intra-DAS Port
and ENNI Link 2 Ports in the right node.
Unprotected EC #4 has its NO MEP, SP MIP
and ENNI MEP functions on ENNI Link 1 Port.
NO: Network Operator, SP: Service Provider
Protected EC #2’s active GW is right, and its
NO MEP, SP MIP and ENNI MEP functions are
on its ENNI Link 2 Port.
Unprotected EC #3 has its NO MEP, SP MIP
and ENNI MEP functions on ENNI Link 2 Port.
See also backup slides
7
Comparison of PB Portal DRNI Data Plane Models I
and II
Model I
Model II


ENNI Link ports







EC Up MEP and EC Down MEP functions are
active for every S-VID
EC MIP functions are active for every S-VID
All EC MIP functions operate on SP MA level
Intra-DAS Link ports
EC MIP functions are active for every S-VID
All EC MIP functions operate on NO MA level
Static EC MEP and MIP activation on
ENNI and Intra-DAS ports
ENNI Link ports



EC Up MEP and EC Down MEP functions may be
active or inactive; active if node is Active GW or if
EC is unprotected, inactive if node is Standby GW
EC MIP functions are active for every S-VID
EC MIP functions may operate at SP or ENNI MA
levels; SP MA level if node is Active GW or if EC
is unprotected, ENNI MA level if node is Standby
GW
Intra-DAS Link ports
 EC Up MEP and EC Down MEP functions
may be active or inactive; active if node is
Active GW, inactive if node is Standby GW
 EC MIP functions are active for every S-VID
 EC MIP functions may operate at SP or
ENNI MA levels; SP MA level if node is
Active GW, ENNI MA level if node is
Standby GW
Dynamic EC MEP and MIP activation
on ENNI and Intra-DAS ports
8
PBB IB-BEB Portal DRNI Data Plane Model
9
PBB IB-BEB Portal DRNI Data Plane Model
(separate B- and S-VLAN fabrics)
S-Relay
EC NO
MEP
EC SP/ENNI
MIP
EC ENNI
MEP
ENNI
Link MEP
S-Relay
Half-DAS
Half-DAS
19.2/3/5
19.2/3/5
19.2/3/5
EC NO/ENNI MIP
19.2/3/5
6.9, 9.5b
6.9 6.9
6.9 6.9 6.9
6.9
6.9 6.9
6.9 6.9 6.9
6.9
6.9, 9.5b
8.5
8.5 8.5
8.5 8.5 8.5
8.5
8.5 8.5
8.5 8.5 8.5
8.5
8.5
19.2
6.10
6.10
6.14
6.14
6.7
19.2
6.7
BVLAN end points
802.3
6.14
6.11, 9.5c
6.11, 9.5c
E-NNI
Link 1
BVLAN MEP
19.2/3/5
19.2/3/5
6.9, 9.5b
Link
MEP
NO: Network Operator, SP: Service Provider
E-NNI
Link 2
19.2/3/5
B-Relay
BVLAN MIP
802.3
6.14
B-Relay
Intra-DAS
Virtual Link
19.2/3/5
6.9, 9.5b
8.5
8.5
19.2
19.2
6.7
6.7
802.n
802.n
These functions
support the
BVLAN
connections and
can be removed
from the view;
see next slide
10
PBB IB-BEB Portal DRNI Data Plane Model
(separate B- and S-VLAN fabrics)
S-MAC space
S-Relay
EC NO
MEP
EC SP
MIP
EC E-NNI
MEP
ENNI
Link MEP
S-Relay
Half-DAS
19.2/3/5
Half-DAS
19.2/3/5
19.2/3/5
EC NO MIP
19.2/3/5
6.9, 9.5b
6.9 6.9
6.9 6.9 6.9
6.9
6.9 6.9
6.9 6.9 6.9
6.9
6.9, 9.5b
8.5
8.5 8.5
8.5 8.5 8.5
8.5
8.5 8.5
8.5 8.5 8.5
8.5
8.5
19.2
6.10
6.10
6.14
6.14
6.7
802.3
E-NNI
Link 1
19.2
6.7
6.14
6.14
6.11, 9.5c
6.11, 9.5c
19.2/3/5
B-MAC space
BVLAN MEP
19.2/3/5
Intra-DAS BVLAN
(Virtual Link)
The DAS function operates in the S-MAC space
c6.10: S-MAC B-MAC
c6.11: BSI Group Address  Default Backbone Destination
(DBD); DBD = {CBP, Group} Address
802.3
E-NNI
Link 2
BVLAN connections
represent the lower
layers
BVLAN connections replace the Ethernet Link connections
in the PB case. SVLAN EC examples are very similar to
SVLAN EC examples in PB case
11
PBB IB-BEB Portal DRNI Data Plane Model
(separate B- and S-VLAN fabrics)
S-MAC space
S-Relay
EC NO
MEP
EC SP
MIP
EC E-NNI
MEP
ENNI
Link MEP
S-Relay
Half-DAS
19.2/3/5
Half-DAS
19.2/3/5
19.2/3/5
EC NO MIP
19.2/3/5
6.9, 9.5b
6.9 6.9
6.9 6.9 6.9
6.9
6.9 6.9
6.9 6.9 6.9
6.9
6.9, 9.5b
8.5
8.5 8.5
8.5 8.5 8.5
8.5
8.5 8.5
8.5 8.5 8.5
8.5
8.5
19.2
MUX
6.10
MUX
MUX
6.14
6.10
MUX
6.7
802.3
E-NNI
Link 1
19.2
6.14
6.7
6.14
6.14
6.11, 9.5c
6.11, 9.5c
19.2/3/5
B-MAC space
BVLAN MEP
19.2/3/5
Intra-DAS BVLAN
(Virtual Link)
802.3
E-NNI
Link 2
BVLAN connections
represent the lower
layers
The functionality of the clause 6.9, 9.5b, 8.5, 6.14, 6.14 and 6.11 functions on PIP/CBP can be
summarized as a (set of) S-VLAN into B-VLAN ‘MUX’ function(s).
PBB data plane model is now very similar with PB data plane model; PBB has a Intra-DAS
(BVLAN) virtual link, where PB has a Intra-DAS link.
12
PBB IB-BEB Portal DRNI Data Plane Models I and II
The behaviour is the same as for the PB Portal DRNI Data
Plane Models I and II
13
PBB-TE IB-BEB Portal DRNI Data Plane Model
14
PBB-TE IB-BEB Portal DRNI Data Plane Model
(separate TESI and S-VLAN fabrics)
S-Relay
EC NO
MEP
EC SP
MIP
EC E-NNI
MEP
ENNI
Link MEP
S-Relay
Half-DAS
Half-DAS
19.2/3/5
19.2/3/5
19.2/3/5
EC NO MIP
19.2/3/5
6.9, 9.5b
6.9 6.9
6.9 6.9 6.9
6.9
6.9 6.9
6.9 6.9 6.9
6.9
6.9, 9.5b
8.5
8.5 8.5
8.5 8.5 8.5
8.5
8.5 8.5
8.5 8.5 8.5
8.5
8.5
19.2
6.10
6.10
6.14
6.14
6.7
19.2
6.7
TESI end points
802.3
6.14
6.11, 9.5c
6.11, 9.5c
E-NNI
Link 1
19.2/3/5
TESI MEP
Link
MEP
TESI-Relay
19.2/3/5
6.9, 9.5b
E-NNI
Link 2
19.2/3/5
TESI-Relay
TESI MIP
802.3
6.14
19.2/3/5
Intra-DAS
Virtual Link
6.9, 9.5b
8.5
8.5
19.2
19.2
6.7
6.7
802.n
802.n
These functions
support the TESI
connections and
can be removed
from the view; see
next slide
15
PBB-TE IB-BEB Portal DRNI Data Plane Model
(separate TESI and S-VLAN fabrics)
S-MAC space
S-Relay
EC NO
MEP
EC SP
MIP
EC E-NNI
MEP
ENNI
Link MEP
S-Relay
Half-DAS
19.2/3/5
Half-DAS
19.2/3/5
19.2/3/5
EC NO MIP
19.2/3/5
6.9, 9.5b
6.9 6.9
6.9 6.9 6.9
6.9
6.9 6.9
6.9 6.9 6.9
6.9
6.9, 9.5b
8.5
8.5 8.5
8.5 8.5 8.5
8.5
8.5 8.5
8.5 8.5 8.5
8.5
8.5
19.2
6.10
6.10
6.14
6.14
6.7
802.3
E-NNI
Link 1
19.2
6.7
6.14
6.14
6.11, 9.5c
6.11, 9.5c
19.2/3/5
TESI MEP
ESP-MAC space
19.2/3/5
802.3
E-NNI
Link 2
Intra-DAS TESI
(Virtual Link)
16
PBB-TE IB-BEB Portal DRNI Data Plane Model
(separate TESI and S-VLAN fabrics)
S-MAC space
S-Relay
EC NO
MEP
EC SP
MIP
EC E-NNI
MEP
ENNI
Link MEP
S-Relay
Half-DAS
19.2/3/5
Half-DAS
19.2/3/5
19.2/3/5
EC NO MIP
19.2/3/5
6.9, 9.5b
6.9 6.9
6.9 6.9 6.9
6.9
6.9 6.9
6.9 6.9 6.9
6.9
6.9, 9.5b
8.5
8.5 8.5
8.5 8.5 8.5
8.5
8.5 8.5
8.5 8.5 8.5
8.5
8.5
19.2
MUX
6.10
MUX
MUX
6.14
6.10
MUX
6.7
802.3
E-NNI
Link 1
19.2
6.14
6.7
6.14
6.14
6.11, 9.5c
6.11, 9.5c
19.2/3/5
TESI MEP
ESP-MAC space
19.2/3/5
802.3
E-NNI
Link 2
Intra-DAS TESI
(Virtual Link)
The functionality of the clause 6.9, 9.5b, 8.5, 6.14, 6.14 and 6.11 functions on PIP/CBP can be
summarized as a (set of) S-VLAN into TESI ‘MUX’ function(s).
PBB-TE data plane model is now very similar with PB data plane model; PBB-TE has a Intra-DAS
(TESI) virtual link, where PB has a Intra-DAS link.
17
PBB-TE IB-BEB Portal DRNI Data Plane Models I and
II
The behaviour is the same as for the PB Portal DRNI Data
Plane Models I and II
18
EOTN TB Portal DRNI Data Plane Model
19
EOTN TB Portal DRNI Data Plane Model
(separate ODUk and S-VLAN fabrics)
S-Relay
EC NO
MEP
EC SP
MIP
EC E-NNI
MEP
ENNI
Link MEP
S-Relay
Half-DAS
Half-DAS
19.2/3/5
19.2/3/5
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
6.15
19.2
19.2/3/5
EC NO MIP
ODUk end points
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
8.5
8.5
6.15
6.15
6.15
ODUk MEP
6.7
802.3
19.2
6.7
ODUk-Relay
802.3
ODUk-Relay
ODU MUX
E-NNI
Link 1
19.2/3/5
ODU MUX
OTN Link
MEP
Intra-DAS
Virtual Link
E-NNI
Link 2
These functions
support the ODUk
connections and
can be removed
from the view; see
next slide
20
EOTN TB Portal DRNI Data Plane Model
(separate ODUk and S-VLAN fabrics)
S-MAC space
S-Relay
EC NO
MEP
EC SP
MIP
EC E-NNI
MEP
ENNI
Link MEP
S-Relay
Half-DAS
Half-DAS
19.2/3/5
19.2/3/5
19.2/3/5
EC NO MIP
19.2/3/5
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
8.5
8.5
8.5
8.5
6.15
6.15
6.15
6.15
19.2
6.7
ODUk MEP
6.7
802.3
E-NNI
Link 1
19.2
802.3
Intra-DAS ODUk
(Virtual Link)
ODUk connections
represent the lower
layers
E-NNI
Link 2
21
EOTN TB Portal DRNI Data Plane Model
(separate ODUk and S-VLAN fabrics)
S-MAC space
S-Relay
EC NO
MEP
EC SP
MIP
EC E-NNI
MEP
ENNI
Link MEP
S-Relay
Half-DAS
19.2/3/5
Half-DAS
19.2/3/5
19.2/3/5
EC NO MIP
19.2/3/5
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
MUX
8.5
MUX
8.5
MUX
8.5
MUX
8.5
6.15
6.15
6.15
6.15
19.2
6.7
ODUk MEP
6.7
802.3
E-NNI
Link 1
19.2
802.3
Intra-DAS ODUk
(Virtual Link)
ODUk connections
represent the lower
layers
E-NNI
Link 2
The functionality of the clause 6.9, 9.5b, 8.5 and 6.15 functions on ONP can be summarized as a
(set of) S-VLAN into ODUk ‘MUX’ function(s).
EOTN TB data plane model is now very similar with PB data plane model; EOTN TB has a IntraDAS (ODUk) virtual link, where PB has a Intra-DAS link.
22
EOTN TB Portal DRNI Data Plane Models I and II
The behaviour is the same as for the PB Portal DRNI Data
Plane Models I and II
23
Summary
EC DRNI functionality is independent of the network technology deployed in a
carrier network and used for the Intra-DAS Link



Intra-DAS Link is either supported by an Ethernet Link, a BVLAN based virtual link, a TESI
based virtual link, or an ODUk based virtual link
DRNI operation is agnostic to the specific Intra-DAS link type
A Generic DRNI Data Plane Model can be used for further DRNI specific architecture
considerations
Data Plane Models I and II deploy the same data plane; the difference between
the two models is the location of the EC NO MEP and EC ENNI MEP functions


Model I has those MEPs only on ENNI Link ports  less complex model
Model II has those MEPs on ENNI Link and Intra-DAS Link ports  more complex model
24
Generic DRNI Data Plane Model
DRNI Data Plane Models can be addressed in a generic, Intra-DAS Link
technology agnostic manner
The link or virtual link between the two nodes in a portal may be shared by
Intra-DAS and Network ECs. See top figure in next slide.
Alternatively, Intra-DAS ECs and Network ECs are carried over dedicated
links or virtual links. See bottom figure in next slide.
The EC NO MEP, EC SP MIP, EC ENNI MEP and EC NO MIP function allocation
in the DRNI is however agnostic to those shared/dedicated (virtual) link cases
25
Generic DRNI Data Plane Model
S-Relay
EC NO
MEP
EC SP/ENNI
MIP
EC ENNI
MEP
Half-DAS
19.2/3/5
Half-DAS
19.2/3/5
6.9, 9.5b
Intra-DAS (Virtual) Link
single (virtual) link
endpoint
6.7
the (virtual) link may be shared by single (virtual) link
Intra-DAS ECs and Network ECs
endpoint
19.2/3/5
8.5
19.2/3/5
EC NO/ENNI MIP
MUX
MUX
19.2/3/5
MUX
Server MEP
19.2
802.3
multiple virtual link
endpoints
Intra-DAS ECs may use a
dedicated (virtual) link.
Network ECs may use
another (virtual) link.
6.9, 9.5b
8.5
19.2
Intra-DAS (Virtual) Link
6.7
E-NNI
Link 1
E-NNI
Link 2
Half-DAS
19.2/3/5
MUX
802.3
S-Relay
Half-DAS
6.9, 9.5b
ENNI
Link MEP
8.5
19.2
S-Relay
EC NO
MEP
EC SP/ENNI
MIP
EC ENNI
MEP
6.9, 9.5b
Server MEP
6.7
E-NNI
Link 1
19.2/3/5
MUX
19.2
802.3
19.2/3/5
EC NO/ENNI MIP
MUX
8.5
ENNI
Link MEP
S-Relay
6.7
802.3
multiple virtual link
endpoint
E-NNI
Link 2
26
MAC Address Considerations
27
EUI48 value allocation (@A, @B, @C, @D)
S-Relay
S-Relay
Half-DAS
19.2/3/5
Half-DAS
19.2/3/5
19.2/3/5
@A @B
6.9, 9.5b
@C @D
MUX
8.5
19.2/3/5
6.9, 9.5b
MUX
8.5
19.2
19.2
Intra-DAS (Virtual) Link
6.7
6.7
802.3
802.3
Physical subsystems (e.g. ports) have an EUI48 value. ENNI and Intra-DAS
Link ports in a two node portal may have EUI48 values @A, @B, @C, @D
as illustrated in the figures above and below. By default, the MAC Source
Address value of primitives generated on those ports inherit the port’s
EUI48 value. Is there a requirement to overrule the inheriting of
E-NNI
Link 1
E-NNI
Link 2
local EUI48 value for a MAC Source Address within DRNI?
S-Relay
S-Relay
Half-DAS
19.2/3/5
Half-DAS
19.2/3/5
19.2/3/5
@A @B
6.9, 9.5b
8.5
MUX
@C @D
MUX
MUX
19.2
6.7
802.3
E-NNI
Link 1
19.2/3/5
MUX
6.9, 9.5b
8.5
19.2
Intra-DAS (Virtual) Link
6.7
802.3
E-NNI
Link 2
28
MAC Address Considerations for Generic DRNI
Data Plane Model I’s EC ENNI MA and EC NO MA
29
Generic DRNI Data Plane Model I
EC ENNI MA
S-Relay
S-Relay
Half-DAS
19.2/3/5
Half-DAS
19.2/3/5
EC NO MIP
EC NO MIP
@A @B
6.9, 9.5b
19.2
19.2
6.9, 9.5b
MUX
Server MEP
Server MEP
8.5
19.2
19.2
Intra-DAS (Virtual) Link
6.7
6.7
802.3
The EC ENNI MAs are fixed MAs; MEP ID and MA ID values in
each EC ENNI MEP can be configured permanently; MAC SA
values can be inherited from the EUI48 value of ports
(@A,@D,@a,@d)
E-NNI
Link 2
802.3
802.3
6.7
6.7
Intra-DAS (Virtual) Link
19.2
19.2
8.5
Server MEP
Server MEP
MUX
@c
@d
19.2/3/5
19.2/3/5
6.9, 9.5b
Half-DAS
S-Relay
19.2
19.2
MUX
@b
EC NO MIP
EC NO MIP
19.2/3/5
S-Relay
ENNI
Link MEP
8.5
@a
6.9, 9.5b
19.2/3/5
Half-DAS
EC ENNI MA
802.3
E-NNI
Link 1
ENNI Link
MEP
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
ENNI
Link MEP
19.2/3/5
@C @D
MUX
8.5
19.2/3/5
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
ENNI Link
MEP
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
30
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
Generic DRNI Data Plane Model I
4 alternative P2P EC Network Operator (NO) MAs
Three alternatives for the operation of these two EC NO MEP functions in the two nodes in a carrier’s portal:
1. Behave as two independent MEP functions with their own MEPID (2, 3) and their own MAC Address (@A, @D)
2. Behave as one virtual MEP function with the same MEPID (2) but with different MAC Addresses (@A, @D)
3. Behave as one virtual MEP function with the same MEPID (2) and the same MAC address (@S)
Standby GW
Active GW
S-Relay
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
Half-DAS
19.2/3/5
Half-DAS
19.2/3/5
EC NO MIP
EC NO MIP
@A @B
6.9, 9.5b
8.5
ENNI
Link MEP
S-Relay
19.2
6.7
19.2/3/5
@C @D
MUX
19.2
19.2/3/5
MUX
Server MEP
Server MEP
19.2
Intra-DAS (Virtual) Link
802.3
6.9, 9.5b
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
8.5
19.2
ENNI Link
MEP
6.7
802.3
E-NNI
Link 1
E-NNI
Link 2
P2P EC Network Operator MA
MEPID=1
animated slide
31
Generic DRNI Data Plane Model I
4 alternative MP EC Network Operator (NO) MAs
Three alternatives for the operation of these two EC NO MEP functions in the two nodes in a carrier’s portal:
1. Behave as two independent MEP functions with their own MEPID (4, 5) and their own MAC Address (@A, @D)
2. Behave as one virtual MEP function with the same MEPID (4) but with different MAC Addresses (@A, @D)
3. Behave as one virtual MEP function with the same MEPID (4) and the same MAC address (@S)
Standby GW
Active GW
S-Relay
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
Half-DAS
19.2/3/5
Half-DAS
19.2/3/5
EC NO MIP
EC NO MIP
@A @B
6.9, 9.5b
8.5
Link
MEP
S-Relay
19.2
6.7
19.2/3/5
@C @D
MUX
19.2
19.2/3/5
MUX
Server MEP
Server MEP
19.2
Intra-DAS (Virtual) Link
6.9, 9.5b
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
8.5
19.2
ENNI Link
MEP
6.7
802.3
802.3
E-NNI
Link 1
E-NNI
Link 2
MP EC Network Operator MA
MEPID=2
MEPID=3
animated slide
MEPID=1
32
Comparing alternatives 1, 2 and 3 from MEP operation
Y.1731 Ethernet OAM and G.8021 Ethernet Equipment support the use of unicast DA values for
MCC, LMM/R 1DM, DMM/R and SLM/R OAM. In P2P EC cases, multicast DA values for MCC,
LMM, 1DM, DMM and SFM may be used instead of unicast DA values.
Alternative 1 P2P EC
Alternative 2 P2P EC
Alternative 3 P2P EC





EC NO MEP functions may
deploy multicast DA values;
agnostic to different MAC
Address values
MEP #1 will detect loss of CCM
from either MEP #2 or MEP #3
Either MEP #2 or MEP #3 will
detect loss of CCM from MEP
#1


Alternative 1 MP EC



Same loss of CCM issue
EC NO MEP functions must
deploy unicast DA values for
MCC, LMM, 1DM, DMM and
SLM
MEPs #1, #2, #3 will have to
adapt their unicast DA value for
MCC, LMM, 1DM, DMM and
SLM when the active ENNI
Link is changed; currently not
supported in G.798
P2P & MP EC OAM problems
EC NO MEP functions may
deploy multicast DA values;
agnostic to different MAC
Address values
No loss of CCM detection in
MEP #1 as MEP #2/#3 have
same MEPID (2)
Either MEP #2 or MEP #3 will
detect loss of CCM from MEP
#1; should be suppressed
under control of Virtual MEP
behaviour


EC NO MEP functions may
deploy multicast DA values;
agnostic to different MAC
Address values
No loss of CCM detection in
MEP #1 as MEP #2/#3 have
same MEPID (2)
Either MEP #2 or MEP #3 will
detect loss of CCM from MEP
#1; should be suppressed
under control of Virtual MEP
behaviour
Alternative 2 MP EC
Alternative 3 MP EC



EC NO MEP functions must
deploy unicast DA values for
MCC, LMM, 1DM, DMM and
SLM
MEPs #1, #2, #3 will have to
adapt their unicast DA value for
MCC, LMM, 1DM, DMM and
SLM when the active ENNI Link
is changed; currently not
supported in G.798
MP EC OAM problems

EC NO MEP functions must
deploy unicast DA values for
MCC, LMM, 1DM, DMM and
SLM
No adaptation of the unicast DA
value for MCC, LMM, 1DM,
DMM and SLM in MEPs #1, #2,
#3 when the active ENNI Link is
changed
No EC OAM problems
33
Summary
From the perspective of the EC Network Operator MEP operation it is helpful
if the EC NO MEP functions in the ENNI Link ports share a common MAC
address (@S). This address @S should be used instead of the local EUI48
values (@A, @D).
All other MEP functions and all the NO MIP functions may use the EUI48 value
of the local port
Question 1: Is it possible to configure the MAC Address of an individual MEP
to overrule the local EUI48 value?
Question 2: From an Ethernet OAM perspective it is possible to operate the
EC SP MIP function on the basis of the EUI48 value of the local port; would
there be an advantage if the EC SP Up Half MIP function deploys the common
MAC address @S in a PBB IB-BEB portal case?
34
MAC Address Considerations for Generic DRNI
Data Plane Model II
35
Generic DRNI Data Plane Model II
4 alternative P2P EC Network Operator (NO) MAs
Three alternatives for the operation of these four EC NO MEP functions in the two nodes in a carrier’s portal:
1. Behave as four independent MEP functions with their own MEPID (2, 3,4,5) and their own MAC Address
(@A,@B,@C,@D)
2. Behave as one virtual MEP function with the same MEPID (2) but with different MAC Addresses (@A,@B,@C,@D)
3. Behave as one virtual MEP function with the same MEPID (2) and the same MAC address (@S)
Standby GW
Active GW
S-Relay
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
Half-DAS
Half-DAS
EC NO MEP
19.2/3/5
19.2/3/5
EC NO MEP
EC SP MIP
EC SP MIP
@A @B
6.9, 9.5b
8.5
Link
MEP
S-Relay
19.2
6.7
19.2/3/5
@C @D
MUX
19.2
19.2/3/5
MUX
Server MEP
Server MEP
19.2
Intra-DAS (Virtual) Link
802.3
6.9, 9.5b
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
8.5
19.2
ENNI Link
MEP
6.7
802.3
E-NNI
Link 1
E-NNI
Link 2
P2P EC Network Operator MA
MEPID=1
animated slide
36
Generic DRNI Data Plane Model II
4 alternative MP EC Network Operator (NO) MAs
Three alternatives for the operation of these four EC NO MEP functions in the two nodes in a carrier’s portal:
1. Behave as four independent MEP functions with their own MEPID (4,5,6,7) and their own MAC Address
(@A,@B,@C,@D)
2. Behave as one virtual MEP function with the same MEPID (4) but with different MAC Addresses (@A,@B,@C,@D)
3. Behave as one virtual MEP function with the same MEPID (4) and the same MAC address (@S)
Standby GW
Active GW
S-Relay
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
Half-DAS
Half-DAS
EC NO MEP
19.2/3/5
19.2/3/5
EC NO MEP
EC SP MIP
EC SP MIP
@A @B
6.9, 9.5b
8.5
Link
MEP
S-Relay
19.2
6.7
19.2/3/5
@C @D
MUX
19.2
19.2/3/5
MUX
Server MEP
Server MEP
19.2
Intra-DAS (Virtual) Link
6.9, 9.5b
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
8.5
19.2
ENNI Link
MEP
6.7
802.3
802.3
E-NNI
Link 1
E-NNI
Link 2
MP EC Network Operator MA
MEPID=2
MEPID=3
animated slide
MEPID=1
37
Generic DRNI Data Plane Model II
Unprotected EC ENNI MA
S-Relay
S-Relay
Half-DAS
Half-DAS
EC NO MEP
19.2/3/5
19.2/3/5
@A @B
6.9, 9.5b
EC NO MIP
EC ENNI MIP
MUX
8.5
ENNI
Link MEP
EC SP MIP
EC ENNI MIP
EC ENNI MEP
19.2
19.2
19.2/3/5
19.2/3/5
@C @D
6.9, 9.5b
MUX
Server MEP
Server MEP
8.5
19.2
19.2
Intra-DAS (Virtual) Link
6.7
6.7
802.3
The Unprotected EC ENNI MAs are fixed MAs; MEP ID and MA
ID values in each EC ENNI MEP can be configured permanently;
MAC SA values can be inherited from the EUI48 value of ports
(@A,@D,@a,@d).
E-NNI
Link 2
802.3
802.3
6.7
6.7
Intra-DAS (Virtual) Link
19.2
19.2
8.5
Server MEP
Server MEP
MUX
@c
@d
19.2/3/5
19.2/3/5
6.9, 9.5b
Half-DAS
S-Relay
19.2
19.2
MUX
@b
EC NO MIP
EC NO MIP
19.2/3/5
S-Relay
ENNI
Link MEP
8.5
@a
6.9, 9.5b
19.2/3/5
Half-DAS
EC ENNI MA
802.3
E-NNI
Link 1
ENNI Link
MEP
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
EC SP MIP
C ENNI MIP
EC ENNI
MEP
EC NO
MEP
EC SP MIP
EC ENNI MIP
EC ENNI
MEP
ENNI Link
MEP
EC NO
MEP
38
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
Generic DRNI Data Plane Model II
8 alternative DRNI Protected EC ENNI MAs
S-Relay
Half-DAS
19.2/3/5
Half-DAS
19.2/3/5
@A @B
6.9, 9.5b
EC NO MEP
EC SP MIP
EC ENNI MIP
EC SP MIP
EC ENNI MIP
EC ENNI MEP
EC ENNI MEP
MUX
8.5
19.2
19.2
19.2/3/5
19.2/3/5
@C @D
6.9, 9.5b
MUX
Server MEP
Server MEP
8.5
19.2
19.2
Intra-DAS (Virtual) Link
6.7
802.3
The DRNI protected EC ENNI MAs are dynamic MAs; their
configuration depends on the location of the Active Gateway in
each Portal. Each EC has eight alternative ENNI MA
configurations in this basic DRNI architecture. COMPLEX!!
E-NNI
Link 2
802.3
802.3
6.7
6.7
Intra-DAS (Virtual) Link
19.2
19.2
8.5
Server MEP
Server MEP
MUX
@c
@d
19.2/3/5
19.2/3/5
6.9, 9.5b
Half-DAS
S-Relay
19.2
19.2
MUX
EC NO MEP
EC SP MIP
EC ENNI MIP
EC ENNI MEP
EC NO MEP
EC ENNI MEP
EC SP MIP
EC ENNI MIP
@b
19.2/3/5
8.5
@a
6.9, 9.5b
19.2/3/5
Half-DAS
ENNI
Link MEP
EC ENNI
MEP
EC NO
MEP
EC SP MI
EC ENNI
S-Relay
animated slide
ENNI Link
MEP
6.7
802.3
E-NNI
Link 1
EC NO
MEP
EC SP MIP
EC ENNI MIP
EC ENNI
MEP
EC NO
MEP
EC SP MIP
C ENNI MIP
EC ENNI
MEP
ENNI
Link MEP
EC NO MEP
ENNI Link
MEP
EC NO
MEP
EC SP MIP
C ENNI MIP
EC ENNI
MEP
S-Relay
39
Comparison of DRNI Data Plane Models I and II
Model I has
Model II has

Very simple and fixed EC ENNI MA
architecture for unprotected and DRNI
protected ECs

Four alternative EC Network Operator MA
configurations with endpoints on the E-NNI
Link ports
Fixed configuration of EC’s







Network Operator MEP,
Service Provider MIP,
ENNI MEP and
Network Operator MIP functions
Simple operation & management


Very simple and fixed EC ENNI MA
architecture for unprotected Ecs
Very complex and dynamic EC ENNI MA
architecture for DRNI protected ECs with
already eight alternative configurations for a
basic DRNI architecture
Four alternative EC Network Operator MA
configurations with endpoints on the E-NNI
and Intra-DAS Link ports
Dynamic configuration of EC’s




Network Operator MEP,
Service Provider MIP,
ENNI MEP and
ENNI MIP functions
Complex operation & management
40
Conclusion
DRNI Data Plane Model II introduces unnecessary operational and
management complexity
Therefore we should select DRNI Data Plane Model I for inclusion in
p802.1AXbq
From an Ethernet OAM perspective, the






Network Operator MEP functions on the ENNI Link ports for a DRNI protected EC should deploy
a common MAC address, overruling the local EUI48 value
Network Operator MEP functions in unprotected ECs and ENNI MEP functions for all ECs on
ENNI Link ports should deploy the local EUI48 value as their MAC address
Network Operator MIP functions for ECs on Intra-DAS Link ports should deploy the local EUI48
as their MAC address
Service Provider MIP functions for unprotected ECs should use the local EUI48 value as their
MAC address
Service Provider Down Half MIP functions for DRNI protected ECs should use the local EUI48
value as their MAC address
Service Provider Up Half MIP functions for a DRNI protected EC could use the local EUI48
value as their MAC address, but in a PBB IB-BEB portal it might be beneficial to use a common
MAC address, overruling the local EUI48 value (for further study)
41
Backup
EC MEP/MIP locations in Data Plane Models I and II
42
PB Data Plane Model I of DRNI functionality
All ECs: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
EUI48:
MAC:
@P
@S
@O
@S
@K
@K
@L
@L
S-Relay
@R
@S
@Q
@S
S-Relay
Half-DAS
Half-DAS
19.2/3/5
19.2/3/5
19.2/3/5
19.2/3/5
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
8.5
8.5
19.2
19.2
19.2
19.2
6.7
6.7
6.7
6.7
802.3
802.3
802.3
802.3
Link MEP
Link MEP
E-NNI
Link 1
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
ENNI Link
MEP
E-NNI
Link 2
Intra-DAS Link
Protected EC
#1
NO MEP
SP MIP
ENNI MEP
NO: Network Operator, SP: Service Provider
43
PB Data Plane Model I of DRNI functionality
All ECs: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
EUI48:
MAC:
@P
@S
@O
@S
@K
@K
@L
@L
S-Relay
@R
@S
@Q
@S
S-Relay
Half-DAS
Half-DAS
19.2/3/5
19.2/3/5
19.2/3/5
19.2/3/5
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
8.5
8.5
19.2
19.2
19.2
19.2
6.7
6.7
6.7
6.7
802.3
802.3
802.3
802.3
EC NO MIP
EC NO MIP
Link MEP
Link MEP
E-NNI
Link 1
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
ENNI Link
MEP
E-NNI
Link 2
Intra-DAS Link
Protected EC
#1
NO MIP
NO: Network Operator, SP: Service Provider
NO MIP
NO MEP
SP MIP
ENNI MEP
44
PB Data Plane Model I of DRNI functionality
All ECs: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
EUI48:
MAC:
@P
@S
@O
@S
@K
@K
@L
@L
S-Relay
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
Link
MEP
@R
@S
@Q
@S
S-Relay
Half-DAS
Half-DAS
19.2/3/5
19.2/3/5
19.2/3/5
19.2/3/5
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
8.5
8.5
19.2
19.2
19.2
19.2
6.7
6.7
6.7
6.7
802.3
802.3
802.3
802.3
EC NO MIP
EC NO MIP
Link MEP
Link MEP
E-NNI
Link 1
E-NNI
Link 2
Intra-DAS Link
Protected EC
#1
NO MEP
SP MIP
ENNI MEP
NO: Network Operator, SP: Service Provider
NO MIP
NO MIP
45
PB Data Plane Model I of DRNI functionality
All ECs: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
EUI48:
MAC:
@P
@S
@O
@S
@K
@K
@L
@L
S-Relay
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
Link
MEP
@R
@S
@Q
@S
S-Relay
Half-DAS
Half-DAS
19.2/3/5
19.2/3/5
19.2/3/5
19.2/3/5
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
8.5
8.5
19.2
19.2
19.2
19.2
6.7
6.7
6.7
6.7
802.3
802.3
802.3
802.3
E-NNI
Link 1
E-NNI
Link 2
Intra-DAS Link
Protected EC
#1
NO MEP
SP MIP
ENNI MEP
NO: Network Operator, SP: Service Provider
46
PB Data Plane Model II of DRNI functionaltiy
Protected EC: NO MEP, EC SP MIP, EC ENNI MEP on Active Gateway
Unprotected EC: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
EUI48:
MAC:
@P
@S
@O
@S
@K
@K
@L
@L
S-Relay
@R
@S
@Q
@S
S-Relay
Half-DAS
Half-DAS
19.2/3/5
19.2/3/5
19.2/3/5
19.2/3/5
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
8.5
8.5
19.2
19.2
19.2
19.2
6.7
6.7
6.7
6.7
802.3
802.3
802.3
802.3
E-NNI
Link 1
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
ENNI Link
MEP
E-NNI
Link 2
Intra-DAS Link
Protected EC
#1
NO MEP
SP MIP
ENNI MEP
NO: Network Operator, SP: Service Provider
47
PB Data Plane Model II of DRNI functionaltiy
Protected EC: NO MEP, EC SP MIP, EC ENNI MEP on Active Gateway
Unprotected EC: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
EUI48:
MAC:
@P
@S
@O
@S
@K
@K
@L
@L
S-Relay
@R
@S
@Q
@S
S-Relay
Half-DAS
Half-DAS
EC NO MEP
19.2/3/5
19.2/3/5
EC SP MIP
EC ENNI MIP
19.2/3/5
19.2/3/5
EC ENNI
MIP
EC ENNI MEP
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
8.5
8.5
19.2
19.2
19.2
19.2
6.7
6.7
6.7
6.7
802.3
802.3
802.3
802.3
Link MEP
Link MEP
E-NNI
Link 1
ENNI Link
MEP
E-NNI
Link 2
Intra-DAS Link
Protected EC
#1
NO MEP
SP MIP
ENNI MEP
NO: Network Operator, SP: Service Provider
ENNI MIP
ENNI MIP
48
PB Data Plane Model II of DRNI functionaltiy
Protected EC: NO MEP, EC SP MIP, EC ENNI MEP on Active Gateway
Unprotected EC: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
EUI48:
MAC:
@P
@S
@O
@S
@K
@K
@L
@L
S-Relay
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
Link
MEP
@R
@S
@Q
@S
S-Relay
Half-DAS
Half-DAS
19.2/3/5
19.2/3/5
19.2/3/5
19.2/3/5
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
8.5
8.5
19.2
19.2
19.2
19.2
6.7
6.7
6.7
6.7
802.3
802.3
802.3
802.3
EC NO MIP
EC NO MIP
Link MEP
Link MEP
E-NNI
Link 1
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
ENNI Link
MEP
E-NNI
Link 2
Intra-DAS Link
Protected EC
#1
ENNI MIP
ENNI MIP
NO: Network Operator, SP: Service Provider
NO MEP
SP MIP
ENNI MEP
49
PB Data Plane Model II of DRNI functionaltiy
Protected EC: NO MEP, EC SP MIP, EC ENNI MEP on Active Gateway
Unprotected EC: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
EUI48:
MAC:
@P
@S
@O
@S
@K
@K
@L
@L
S-Relay
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
Link
MEP
@R
@S
@Q
@S
S-Relay
Half-DAS
Half-DAS
19.2/3/5
19.2/3/5
19.2/3/5
19.2/3/5
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
6.9, 9.5b
8.5
8.5
8.5
8.5
19.2
19.2
19.2
19.2
6.7
6.7
6.7
6.7
802.3
802.3
802.3
802.3
EC NO MIP
EC NO MIP
Link MEP
Link MEP
E-NNI
Link 1
EC NO
MEP
EC SP
MIP
EC ENNI
MEP
ENNI Link
MEP
E-NNI
Link 2
Intra-DAS Link
Protected EC
#1
NO MEP
SP MIP
ENNI MEP
NO: Network Operator, SP: Service Provider
50
MAC Address & MEP ID
DRNI presents the Network Operator
(NO) MEP functions for an EC on the
different E-NNI ports as one virtual
NO MEP function with one S-MAC
Address and one MEP ID
Question: Is the same MEP ID really
required? Evaluate requirement from
perspective of:
Question: Is the same S-MAC address
really required? Evaluate requirement
from perspective of:
DRNI presents the Service Provider
(SP) MIP functions for an EC on the
different E-NNI ports as one virtual
SP MIP function with one S-MAC
Address
•
CFM (CCM, LBM/R, SLM/R, LMM/R,
DMM/R, …) between NO MEP on UNI-N and
E-NNI ports and MIP functions on I-NNI ports
inside carrier network
•
CFM (CCM) between NO MEP functions on
UNI-N and E-NNI ports
Question: Is the same S-MAC address
really required? Evaluate requirement
from perspective of:
•
B-MAC learning inside B-VLAN relays
•
S-MACB-MAC learning inside c6.10 PIP
function
•
CFM (LBM/R, LTM/R) between SP MEPs on
UNI-N ports and SP MIPs on E-NNI ports
•
Translation of ‘BSI Group Address’ into
‘Default Backbone Destination (DBD)’ (and
vice versa) inside c6.11 CBP function
•
B-MAC learning inside B-VLAN relays
•
S-MACB-MAC learning inside c6.10 PIP
function
51
MAC Address & MEP ID
DRNI presents the E-NNI MEP
functions for an EC on the different
E-NNI ports as one virtual E-NNI MEP
function with one S-MAC Address
and one MEP ID
Question: Is the same S-MAC address
really required? Evaluate requirement
from perspective of:
•
CFM (CCM, LBM/R, SLM/R, LMM/R,
DMM/R, …) between E-NNI MEP functions
(Data Plane Model I), or between E-NNI
MEP functions on E-NNI or Intra-DAS ports
and DRNI MIP functions on Intra-DAS or ENNI ports (Model II)
•
S-MAC learning inside S-VLAN relays in
DRNI
Question: Is the same MEP ID really
required? Evaluate requirement from
perspective of:
•
CFM (CCM) between E-NNI MEP functions
on E-NNI ports (model I), or E-NNI MEP
functions on E-NNI or Intra-DAS ports
(model II)
52