1 DRNI and Distributed Protection Examples Maarten Vissers v01 Based on slides presented in IW meeting in Nanjing on Thursday Sept 22 Details have been added to reflect the discussions during the presentation MAC Address considerations have been added based on discussions during the presentation and questions have been added triggered by comment that CFM has been developed under the assumption that MAC address of MEP/MIP can be changed during the lifetime of the EC

2 DRNI Objectives Definition of E-NNI includes either  E-NNI links  Intra-DAS link is I-NNI  E-NNI links + Intra-DAS links  How to deal with time sharing network link and intra-DAS link? Network link is I-NNI! DRNI with 2x2 nodes and 2x1 E-NNI links should recover services after failure of one of the four nodes DRNI with 2x2 nodes and 2x2 E-NNI links should recover services after failure of 2x1 of the 2x2 nodes; the X- links enable this capability DRNI can be deployed on  PB portal, PBB IB-BEB portal, PBB-TE IB- BEB portal, OTN TB portal, SDH TB portal, MPLS S-PE portal, MPLS-TP S-PE portal DRNI operation can be added in a hitless manner to existing E-NNI  Similar requirement exist for protection switching of individual service instances  Carrier networks are in operation before inter-carrier services are added  Individual E-NNI interfaces are added to existing nodes  Those nodes are already interconnected via the domain they belong to; i.e. network links already exist  DRNI operation should be added to those E-NNI interfaces, without disturbing the existing ECs DRNI interoperates with the following survivability mechanisms in carrier networks:  ETH SNCP, ERP, ETH CL-SNCG/I protection, TESI protection, ODUk SNCP, tLSP SNCP, VC-n SNCP  MSTP/MVRP, GMPLS,

3 DRNI Objectives – 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 C-MAC Address and one MEP ID Question: Is the same C-MAC address really required? Evaluate requirement from perspective of: 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 B-MAC learning inside B-VLAN relays C-MAC  B-MAC learning inside c6.10 PIP function Translation of ‘BSI Group Address’ into ‘Default Backbone Destination (DBD)’ (and vice versa) inside c6.11 CBP function Question: Is the same MEP ID really required? Evaluate requirement from perspective of: CFM (CCM) between NO MEP functions on UNI-N and E-NNI ports 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 C-MAC Address Question: Is the same C-MAC address really required? Evaluate requirement from perspective of: CFM (LBM/R, LTM/R) between SP MEPs on UNI-N ports and MIPs on E-NNI ports B-MAC learning inside B-VLAN relays C-MAC  B-MAC learning inside c6.10 PIP function

4 DRNI Objectives – 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 C-MAC Address and one MEP ID Question: Is the same C-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 E- NNI ports (Model II) C-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)

5 Distributed Protection Objectives – MAC Address & MEP ID Distributed Protection presents the Working SNCP MEP functions for an EC on the different I-NNI ports as one virtual Working SNCP MEP function with one C-MAC Address and one MEP ID Distributed Protection presents the Protection SNCP MEP functions for an EC on the different I-NNI ports as one virtual Protection SNCP MEP function with one C-MAC Address and one MEP ID Question: Is the same C-MAC address really required? Evaluate requirement from perspective of: CFM (CCM, LBM/R, SLM/R, LMM/R, DMM/R, …) between SNCP MEP on I-NNI ports and MIP functions on I-NNI ports inside carrier network B-MAC learning inside B-VLAN relays C-MAC  B-MAC learning inside c6.10 PIP function Translation of ‘BSI Group Address’ into ‘Default Backbone Destination (DBD)’ (and vice versa) inside c6.11 CBP function Question: Is the same MEP ID really required? Evaluate requirement from perspective of: CFM (CCM) between SNCP MEP functions on I-NNI ports

6 Portal XXX Node 2XXX Node 1 DAS XXX Node 4XXX Node 3 DAS DSS Communication protocols DRNI & DSNCP Half-DAS Half-DSS Half-DAS Half-DSS Half-DAS Half-DSS Half-DAS Half-DSS DAS  DSS DSS  DSS DAS  DAS

7 PB Portal with DRNI; EC SNCP in carrier network Two Data Plane models (I, II) are presented, which differ in the location of the EC Network Operator MEP and EC E-NNI MEP functions I.On E-NNI port; i.e. as close as possible to physical E- NNI link II.On Active Gateway; i.e. either on E-NNI port, or on Intra- DAS port

8 PB Data Plane Model (I) (example with EC SNCP) 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n E-NNI Link 2 I-NNI Link a 19.2/3/5 6.9/9.5b n 19.2/3/5 6.9/9.5b n 19.2/3/5 6.9/9.5b n E-NNI Link 3 I-NNI Link b Half-DAS S-Relay Network Link Intra-DSS Link PNP 19.2/3/5 6.9/9.5b n Half-DSS Half-DAS S-Relay 19.2/3/ b E-NNI Link /3/ b /3/5 6.9/9.5b n E-NNI Link 4 Intra-DAS Link DSS: Distributed SNC protection Sublayer EC NO MEP EC E-NNI MEP EC SP MIP EC NO MIP Link MEP EC SNCP (I-NNI) Network Operator MA has its MEP on E-NNI port. Intra-DAS NNI port has only MIP function, as Intra-DAS link is considered part of operator network. Default mode: MAC Address of MEP and MIP functions is inherited from EUI-48 of NNI Special mode: EUI-48 value is not inherited in the following cases: EC MEP/MIP functions on E-NNI ports must have common MAC Address Working EC SNCP MEP/MIP functions on I-NNI ports must have common MAC Address Protection EC SNCP MEP/MIP functions on I-NNI ports must have common MAC Address EUI48: MAC:

9 PB Data Plane Model I (example with EC SNCP) DSS: Distributed SNC protection Sublayer Intra-DAS link can be combined with Network Link SVIDs 1..M: network link SVIDs M+1..N: intra-DSS link SVIDs N : intra-DAS link 19.2/3/ b n 19.2/3/ b n I-NNI Link a Half-DSS Network Link Intra-DSS Link Intra-DAS @P EUI48: MAC: Per MEP/MIP set MAC Per MEP/MIP set MAC

10 PB Data Plane Model I (example with EC SNCP) 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n E-NNI Link 2 I-NNI Link a 19.2/3/5 6.9/9.5b n 19.2/3/5 6.9/9.5b n 19.2/3/5 6.9/9.5b n E-NNI Link 3 I-NNI Link b Half-DAS S-Relay Network Link Intra-DSS Link PNP 19.2/3/5 6.9/9.5b n Half-DSS Half-DAS S-Relay 19.2/3/ b E-NNI Link /3/ b /3/5 6.9/9.5b n E-NNI Link 4 Intra-DAS Link EC NO MEP EC E-NNI MEP EC SP MIP EC NO MIP Link MEP EC SNCP MEP Half-DSS (I-NNI) X Active E-NNI Gateway for EC Standby E-NNI Gateway for EC Active SNCP Gateway for EC Standby SNCP Gateway for EC EC MIP functions on Standby SNCP Gateway do not need to use common MAC address instead those can inherit MAC address from Now it is possible to do loopback between EC SNCP MEP functions and those EUI48: MAC:

11 PB Data Plane Model I (example with EC SNCP) 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n E-NNI Link 2 I-NNI Link a 19.2/3/5 6.9/9.5b n 19.2/3/5 6.9/9.5b n 19.2/3/5 6.9/9.5b n E-NNI Link 3 I-NNI Link b Half-DAS S-Relay Network Link Intra-DSS Link PNP 19.2/3/5 6.9/9.5b n Half-DSS Half-DAS S-Relay 19.2/3/ b E-NNI Link /3/ b /3/5 6.9/9.5b n E-NNI Link 4 Intra-DAS Link DSS: Distributed SNC protection Sublayer EC NO MEP EC E-NNI MEP EC SP MIP EC NO MIP Link MEP EC SNCP MEP Half-DSS (I-NNI) X Active E-NNI Gateway for EC Standby E-NNI Gateway for EC Standby SNCP Gateway for EC Active SNCP Gateway for EC EC MIP functions on Standby SNCP Gateway do not need to use common MAC address instead those can inherit MAC address from Now it is possible to do loopback between EC SNCP MEP functions and those EUI48: MAC:

12 PB Data Plane Model II (example with EC SNCP) 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n E-NNI Link 2 I-NNI Link a 19.2/3/5 6.9/9.5b n 19.2/3/5 6.9/9.5b n 19.2/3/5 6.9/9.5b n E-NNI Link 3 I-NNI Link b Half-DAS S-Relay Network Link Intra-DSS Link PNP 19.2/3/5 6.9/9.5b n Half-DSS Half-DAS S-Relay 19.2/3/ b E-NNI Link /3/ b /3/5 6.9/9.5b n E-NNI Link 4 Intra-DAS Link DSS: Distributed SNC protection Sublayer EC NO MEP EC E-NNI MEP EC SP MIP EC NO MIP Link MEP EC SNCP MEP Half-DSS (E-NNI) Network Operator MA has its MEP on active Gateway node (i.e. either E-NNI port or Intra-DAS NNI port). Intra-DAS link is considered part of E-NNI. Intra-DAS port contains EC NO MEP and EC E-NNI MEP functions. Default mode: MAC Address of MEP and MIP functions is inherited from EUI-48 of NNI Special mode: EUI-48 value is not inherited in the following cases: EC MEP/MIP functions on E-NNI and Intra-DAS ports must have common MAC Address Working EC SNCP MEP/MIP functions on I-NNI ports must have common MAC Address Protection EC SNCP MEP/MIP functions on I-NNI ports must have common MAC @S EUI48: MAC:

13 PB Data Plane Model II (example with EC SNCP) DSS: Distributed SNC protection Sublayer Intra-DAS link can be combined with Network Link SVIDs 1..M: network link SVIDs M+1..N: intra-DSS link SVIDs N : intra-DAS link 19.2/3/ b n 19.2/3/ b n I-NNI Link a Half-DSS Network Link Intra-DSS Link Intra-DAS @P Per MEP/MIP set MAC @S Per MEP/MIP set MAC

14 PB Data Plane Model II (example with EC SNCP) 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n E-NNI Link 2 I-NNI Link a 19.2/3/5 6.9/9.5b n 19.2/3/5 6.9/9.5b n 19.2/3/5 6.9/9.5b n E-NNI Link 3 I-NNI Link b Half-DAS S-Relay Network Link Intra-DSS Link PNP 19.2/3/5 6.9/9.5b n Half-DSS Half-DAS S-Relay 19.2/3/ b E-NNI Link /3/ b /3/5 6.9/9.5b n E-NNI Link 4 Intra-DAS Link EC NO MEP EC E-NNI MEP EC SP MIP EC NO MIP Link MEP EC SNCP MEP Half-DSS (E-NNI EUI48: MAC: Active E-NNI Gateway for EC Standby E-NNI Gateway for EC Active SNCP Gateway for EC Standby SNCP Gateway for EC EC MIP functions on Standby SNCP Gateway do not need to use common MAC address instead those can inherit MAC address from Now it is possible to do loopback between EC SNCP MEP functions and those

15 PB Data Plane Model II (example with EC SNCP) 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n E-NNI Link 2 I-NNI Link a 19.2/3/5 6.9/9.5b n 19.2/3/5 6.9/9.5b n 19.2/3/5 6.9/9.5b n E-NNI Link 3 I-NNI Link b Half-DAS S-Relay Network Link Intra-DSS Link PNP 19.2/3/5 6.9/9.5b n Half-DSS Half-DAS S-Relay 19.2/3/ b E-NNI Link /3/ b /3/5 6.9/9.5b n E-NNI Link 4 Intra-DAS Link EC NO MEP EC E-NNI MEP EC SP MIP EC NO MIP Link MEP EC SNCP MEP Half-DSS (E-NNI ) X Standby E-NNI Gateway for EC Active E-NNI Gateway for EC Standby SNCP Gateway for EC Active SNCP Gateway for EC EC MIP functions on Standby E-NNI Gateway do not need to use common MAC instead those can inherit MAC address from Now it is possible to do loopback between EC E-NNI MEP functions and those EC MIP functions on Standby SNCP Gateway do not need to use common MAC address instead those can inherit MAC address from Now it is possible to do loopback between EC SNCP MEP functions and those MIP functions.

16 PB Bridge Model of DAS (example with EC SNCP) n b n b n E-NNI Link 2 I-NNI Link a n 6.9/9.5b n 6.9/9.5b n E-NNI Link 3 I-NNI Link b Half-DAS S-Relay Network Link Intra-DSS Link 19.2/3/5 6.9/9.5b n Half-DAS S-Relay E-NNI Link /3/ b n E-NNI Link 4 Intra-DAS Link DSS: Distributed SNC protection Sublayer EC E-NNI MEP EC SP MIP EC NO MIP Link MEP EC SNCP MEP 19.2/3/5 EC NO MEP Steve’s proposal Is there an alternative?

17 PB Logical Bridge Model for DRNI and DSNCP (example with EC SNCP) 19.2/3/ b n 19.2/3/ b n E-NNI Link 2 I-NNI Link a 19.2/3/5 6.9/9.5b n 19.2/3/5 6.9/9.5b n E-NNI Link 3 I-NNI Link b S-Relay Network Link n DSS DAS S-Relay E-NNI Link /3/ b n E-NNI Link 4 DSS: Distributed SNC protection Sublayer S-Relay b b b b /3/ b n I-NNI Link a 19.2/3/5 6.9/9.5b n I-NNI @S DAS  DSS

18 Notes/Observations PB Portal Data Plane Model  Use of MAC Address and at multiple locations reduces ability to perform connectivity fault localization  Physical subsystem is identified either by build in EUI-48 value, or by operator configured EUI-48 value; default MAC Address is inherited from physical subsystem  Distributed protection/restoration introduces requirement to configure MAC Address of selected MEP/MIP sets (on a service instance (EC) basis); not required/supported today  EC NO MA supports endpoint on E-NNI port card  I-NNI port may have to support network link, intra-DSS link and intra-DAS link and the associated MAC Address values Bridge Model of DAS  Removes the ability to localize misconnection in a Half-DAS function due to use of common MAC address values  Require that Intra-DAS link port uses EC NO MEP and EC E-NNI MEP functions  EC NO MA does not always support endpoint on E-NNI port card; instead endpoint may be at active gateway node, and the E-NNI port is behind the Intra-DAS link

19 PBB IB-BEB Portal with DRNI; EC SNCP in carrier network Two Data Plane models (I, II) are possible, which differ in the location of the EC Network Operator MEP and EC E-NNI MEP functions; see PB slides for the differences. Data Plane model I is used in the slides hereafter Two data plane models (1,2) are possible, which differ in the presence of a single or multiple switch fabrics: 1)Separate B-VLAN switch fabric and S-VLAN switch fabric 2)Combined B-/S-VLAN switch fabric

20 Carrier B Carrier A DRNI in PBBN IB-BEBs – Multi-domain PBBN For the case the carrier network consists of multiple PBBN domains (e.g. PBBN 1, PBBN 2), protection of the S-VLAN is not possible by means of B-VLAN recovery under all conditions Instead it will be necessary to protect the individual S-VLAN connections by means of G.8031 ETH SNC Protection. Working and Protection S-VLAN connections must be carried by disjoint B-VLANs in each PBBN and by disjoint LANs between PBBN domains PBBN 1 PBBN 2 PBBN 3 IB-BEB PBB- TEN 4 IB-BEB DSNCP WP SNCP DSNCP

21 PBB Data Plane Model I/1 (separate B- and S-VLAN fabrics) (example with EC SNCP) 19.2/3/5 6.9, 9.5b n 6.9, 9.5b n 6.9, 9.5b n E-NNI Link 2 I-NNI Link a 19.2/3/5 6.9, 9.5b n 6.9, 9.5b n 6.9, 9.5b n E-NNI Link 3 I-NNI Link b Half-DAS S-Relay PIP 19.2/3/5 6.9, 9.5b Half-DAS S-Relay 19.2/3/5 6.9, 9.5b E-NNI Link /3/5 6.9, 9.5b /3/5 6.9, 9.5b E-NNI Link , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/5 PNP , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/5 B-Relay 19.2/3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b 8.5 CBP PNP Network Virtual Link Intra-DAS Virtual Link Intra-DSS Virtual Link Network Link Intra-DSS Link Intra-DAS Link BVLAN MEP Link MEP EC NO MEP EC E-NNI MEP EC SP MIP EC NO MIP Link MEP EC SNCP MEP 19.2/3/5 Half-DSS I-NNI Virtual Link a I-NNI Virtual EUI48: MAC: These functions support the BVLAN connections and can be removed from the view; see next slide

22 PBB Data Plane Model I/1 (separate B- and S-VLAN fabrics) (example with EC SNCP) 19.2/3/5 6.9, 9.5b , 9.5b , 9.5b 8.5 E-NNI Link /3/5 6.9, 9.5b , 9.5b , 9.5b 8.5 E-NNI Link 3 Half-DAS S-Relay PIP 19.2/3/5 6.9, 9.5b Half-DAS S-Relay 19.2/3/5 6.9, 9.5b E-NNI Link /3/5 6.9, 9.5b /3/5 6.9, 9.5b E-NNI Link , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/5 PNP , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/5 CBP Network BVLAN (Virtual Link) Intra-DAS BVLAN (Virtual Link) Intra-DSS BVLAN (Virtual Link) BVLAN MEP EC NO MEP EC E-NNI MEP EC SP MIP EC NO MIP Link MEP EC SNCP MEP EUI48: MAC: BVLAN connections represent the lower layers EUI48: MAC: DAS & DSS in C-MAC space c6.10:C-MAC  B-MAC c6.11: BSI Group Address  Default Backbone Destination (DBD); DBD = {CBP, Group} Address C-MAC space I-NNI BVLAN a (Virtual Link) I-NNI BVLAN (Virtual Link) BVLAN connections replace the Ethernet Link connections in the PB case. EC examples are very similar to EC examples in PB case.

23 PBB Bridge Model of DAS (separate B- and S-VLAN fabrics) (example with EC SNCP) 6.9, 9.5b , 9.5b 8.5 E-NNI Link 2 6.9, 9.5b , 9.5b 8.5 E-NNI Link 3 Half-DAS S-Relay 19.2/3/5 6.9, 9.5b S-Relay 19.2/3/5 6.9, 9.5b E-NNI Link E-NNI Link , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/5 Network Virtual Link Intra-DAS Virtual Link BVLAN MEP Link MEP 19.2/3/5 Half-DSS Half-DAS EC E-NNI MEP EC SP MIP EC NO MIP EC SNCP MEP EC NO I-NNI Virtual Link a I-NNI Virtual Link b B-MAC space C-MAC space Intra-DSS Virtual Link

24 PBB Logical Bridge Model for DRNI and DSNCP (example with EC SNCP) 6.9, 9.5b , 9.5b , 9.5b , 9.5b 8.5 S-Relay /3/ b E-NNI Link /3/5 6.9/9.5b E-NNI Link n DSS DAS E-NNI Link /3/ b n E-NNI Link 4 S-Relay b b @S DAS  DSS , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/5 Network Virtual Link I-NNI Virtual Link a I-NNI Virtual Link b b b , 9.5c 19.2/3/5 I-NNI Virtual Link b , 9.5c 19.2/3/5 I-NNI Virtual Link a

25 B-Relay PBB Data Plane Model I/2 (combined B- and S-VLAN fabrics) (example with EC SNCP) 6.9, 9.5b n PIP , 9.5c 19.2/3/5 6.9, 9.5b 8.5 CBP PNP 19.2/3/5 S-Relay B-Relay HDSS 6.9, 9.5b n , 9.5c 19.2/3/5 6.9, 9.5b /3/5 HDSS S-Relay Data plane model 1 for separate B- & S-VLAN fabrics Data plane model 2 for combined B- & S-VLAN fabrics B-VLAN Relay supports MP BVLAN connectivity between two or more PNPs and one or more CBPs The same connectivity within a IB-BEB with combined B- & S-VLAN Fabric Two PIP/CBP function sets should behave as a single virtual PIP/CBP function set… what does this mean for the allocation of MAC Addresses? n 19.2/3/5 6.9, 9.5b , 9.5b n , 9.5c 19.2/3/5 6.9, 9.5b /3/5 HDSS 6.9, 9.5b , 9.5c 19.2/3/5 HDSS Fabric

26 PBB IB-BEB Portal with DRNI; B-VLAN restoration in carrier network Two data plane models (1,2) are possible, which differ in the presence of a single or multiple switch fabrics: 1)Separate B-VLAN switch fabric and S-VLAN switch fabric 2)Combined B-/S-VLAN switch fabric

27 PBB Data Plane Model I/1 (example with BVLAN restoration) 19.2/3/5 6.9, 9.5b n n 19.2/3/5 6.9, 9.5b n E-NNI Link 2 I-NNI Link a 19.2/3/5 6.9, 9.5b n 19.2/3/5 6.9, 9.5b n 19.2/3/5 6.9, 9.5b n E-NNI Link 3 I-NNI Link b Half-DAS S-Relay PIP 19.2/3/5 6.9, 9.5b Half-DAS S-Relay 19.2/3/5 6.9, 9.5b E-NNI Link /3/5 6.9, 9.5b /3/5 6.9, 9.5b E-NNI Link , 9.5c 19.2/3/ , 9.5c 19.2/3/5 PNP , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/5 B-Relay 19.2/3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b 8.5 CBP PNP Network Virtual Link Intra-DAS Virtual Link Intra-DSS Virtual Link Intra-DAS Link 19.2/3/5 6.9, 9.5b , 9.5c 19.2/3/5 BVLAN MEP Link MEP EC NO MEP EC E-NNI MEP EC SP MIP EC NO MIP Link MEP Network Link Intra-DVS Link Half-DVS DVS: Distributed VLAN restoration Sublayer

28 PBB Data Plane Model I/1 (example with BVLAN restoration) 19.2/3/5 6.9, 9.5b /3/5 6.9, 9.5b 8.5 E-NNI Link /3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b 8.5 E-NNI Link 3 Half-DAS S-Relay PIP 19.2/3/5 6.9, 9.5b Half-DAS S-Relay 19.2/3/5 6.9, 9.5b E-NNI Link /3/5 6.9, 9.5b /3/5 6.9, 9.5b E-NNI Link , 9.5c 19.2/3/ , 9.5c 19.2/3/5 PNP , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/5 CBP Network Virtual Link Intra-DAS Virtual Link 19.2/3/5 6.9, 9.5b , 9.5c 19.2/3/5 BVLAN MEP EC NO MEP EC E-NNI MEP EC SP MIP EC NO MIP Link MEP Half-DVS DVS: Distributed VLAN EUI48: MAC: Intra-DSS Which B-MAC addresses will these BVLAN MEPs (on CBPs) have? Which C-MAC addresses will these EC MIPs (on PIPs) have? Which B-MAC addresses will these PIPs have? B-MAC space C-MAC space

29 PBB-TE IB-BEB Portal with DRNI; TESI protection in carrier network Two data plane models (1,2) are possible, which differ in the presence of a single or multiple switch fabrics: 1)Separate ESP/TESI switch fabric and S-VLAN switch fabric 2)Combined ESP/S-VLAN switch fabric

30 PBB-TE Data Plane Model I/1 (example with TESI protection) 19.2/3/5 6.9, 9.5b n n 19.2/3/5 6.9, 9.5b n E-NNI Link 2 I-NNI Link a 19.2/3/5 6.9, 9.5b n 19.2/3/5 6.9, 9.5b n 19.2/3/5 6.9, 9.5b n E-NNI Link 3 I-NNI Link b Half-DAS S-Relay PIP 19.2/3/5 6.9, 9.5b Half-DAS S-Relay 19.2/3/5 6.9, 9.5b E-NNI Link /3/5 6.9, 9.5b /3/5 6.9, 9.5b E-NNI Link , 9.5c 19.2/3/ , 9.5c 19.2/3/5 PNP , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/5 B-Relay 19.2/3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b 8.5 CBP PNP Network Virtual Link Intra-DAS Virtual Link Intra-DSS Virtual Link Intra-DAS Link 19.2/3/5 6.9, 9.5b , 9.5c 19.2/3/5 TESI MEP Link MEP EC NO MEP EC E-NNI MEP EC SP MIP EC NO MIP Link MEP Network Link Intra-DTS Link Half-DTS DTS: Distributed TESI protection Sublayer

31 PBB-TE Data Plane Model I/1 (example with TESI protection) 19.2/3/5 6.9, 9.5b /3/5 6.9, 9.5b 8.5 E-NNI Link /3/5 6.9, 9.5b /3/5 6.9, 9.5b /3/5 6.9, 9.5b 8.5 E-NNI Link 3 Half-DAS S-Relay PIP 19.2/3/5 6.9, 9.5b Half-DAS S-Relay 19.2/3/5 6.9, 9.5b E-NNI Link /3/5 6.9, 9.5b /3/5 6.9, 9.5b E-NNI Link , 9.5c 19.2/3/ , 9.5c 19.2/3/5 PNP , 9.5c 19.2/3/ , 9.5c 19.2/3/ , 9.5c 19.2/3/5 CBP Network TESI (Virtual Link) Intra-DAS TESI (Virtual Link) 19.2/3/5 6.9, 9.5b , 9.5c 19.2/3/5 TESI MEP EC NO MEP EC E-NNI MEP EC SP MIP EC NO MIP Link MEP Half-DTS DTS: Distributed TESI protection Sublayer Intra-DSS TESI ESP-MAC space EUI48: MAC: Which ESP-MAC addresses will these ESP/TESI MEPs (on CBPs) have?

32 OTN TB Portal with DRNI; ODUk SNCP in carrier network Two data plane models: 1)Separate ODUk switch fabric and Ethernet switch fabric 2)Universal switch fabric

33 OTN TB Portal with DRNI; EC SNCP in carrier network Two data plane models: 1)Separate ODUk switch fabric and Ethernet switch fabric 2)Universal switch fabric

34 MPLS-TP TB Portal with DRNI; Transport-LSP SNCP in carrier network Two data plane models: 1)Separate MPLS-TP switch fabric and Ethernet switch fabric 2)Universal switch fabric

35 MPLS-TP TB Portal with DRNI; EC SNCP in carrier network Two data plane models: 1)Separate MPLS-TP switch fabric and Ethernet switch fabric 2)Universal switch fabric