1 DRNI Examples and DAS position Maarten Vissers Version 01

2 Contents  Version 00 slides (3 to 8)  Figure drawn during Aug. 11 virtual meeting (9 and 10)  Version 01 new slides (11 to 27)  PB Gateway nodes examples –Fault free –E-NNI Link failure –I-NNI Link failure –Gateway node failure  PBBN IB-BEB Gateway nodes examples –Fault free –E-NNI Link failure –I-NNI Link failure –Gateway node failure  PBB-TEN IB-BEB Gateway nodes examples –Fault free –E-NNI Link failure –I-NNI Link failure –Gateway node failure  PBBN B-BEB Gateway nodes examples (to be added in v02)

3 Version 00 slides

4 PBN PBBN PB PBB-TENPBBN B-BEB 1 23 IB-BEB DRNI Three examples DRNI between a PBN and a PBBN is established between two PB nodes and two IB-BEB nodes DRNI between a PBBN and a PBB-TEN is established between four IB-BEB nodes DRNI between two PBBNs is established between four B-BEB nodes

5 The following slides present the three examples by means of their node models with  Port and Relay functions  Clause 6, 8 and 19 shims The objective is to determine where the Distributed Link Aggregation Sublayer (DAS) belongs in the stack of clause 6/8/19 shims  802.1AX specifies the LAG sublayer as a client of the MAC Sublayer; the LAG sublayer is bound by one upper MAC SAP and multiple lower MAC SAPs  In an 802.1D bridge the LAG sublayer would be located below the MAC Relay, presenting the set of true ISS SAPs as one (virtual) ISS SAP to the Relay; the LAG sublayer is then bound by one upper (virtual) ISS SAP and multiple lower ISS SAPs  Discussion: The upper ISS SAP can not be used to instantiate UP/DOWN MEPs and MIPs, as this SAP is a virtual SAP located inside the bridge’s ‘switch fabric’  In an 802.1Q bridge the LAG sublayer should in analogy be located below the MAC Relay, presenting the set of true EISS SAPs as one (virtual) EISS SAP to the Relay; the LAG sublayer is then bound by one upper (virtual) EISS SAP and multiple lower EISS SAPs  Discussion: The upper EISS SAP can not be used to instantiate UP/DOWN MEPs and MIPs, as this SAP is a virtual SAP located inside the bridge’s ‘switch fabric’  Clause 22 of 802.1Q-2011 specifies that the LAG Sublayer is located at the ISS SAP, not at the EISS SAP; it specifies that per VID UP/DOWN MEPs and MIPs can be instantiated between MAC Relay and LAG Sublayer and that only a Link Down MEP can be instantiated below the LAG sublayer.  DRNI however requires that each service instance passes through an UP MEP just before handing the service frames to the E-NNI link

6 PBN PBBN PB IB-BEB 1. PBN – DRNI – PBBN PNP S-VLAN Relay PNP S-VLAN Relay PNP PIP S-VLAN Relay PIP CNP B-VLAN Relay CBP PNP IB-BEB PIP S-VLAN Relay PIP CNP B-VLAN Relay CBP PNP DRNI ? ? 8.6 S-VLAN MAC Relay 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n 19.2,19.3, b n 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n 8.6 S-VLAN MAC Relay 19.2/3/ b /3/ b /3/ b DRNI , 9.5c 19.2/3/5 The Intra-DAS link can be supported by a link (solid line) in the carrier domain (top) or a dedicated link (dotted line) within the DRNI area (bottom) OR DAS Intra-DAS DAS Intra-DAS PNP CNP PNP PIP CBP 8.6 B-VLAN MAC Relay

7 PBBN IB-BEB S-VLAN Relay B-VLAN Relay PNP IB-BEB S-VLAN Relay PIP B-VLAN Relay CBP PNP PBB-TEN IB-BEB 2. PBBN – DRNI – PBB-TEN CNP PIP S-VLAN Relay PIP CNP TESI/ESP B-Relay CBP PNP IB-BEB PIP S-VLAN Relay PIP CNP TESI/ESP B-Relay CBP PNP DRNI PIP CBP PIP CBP PIP CBP PIP CBP PIP CBP PIP CBP PIP CBP PNP ? ? 8.6 S-VLAN MAC Relay 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n 19.2,19.3, b /3/ b n 19.2/3/ b n 19.2/3/ b n 8.6 S-VLAN MAC Relay 19.2/3/ b /3/ b /3/ b ,19.3, b ,19.3, b , 9.5c 19.2/3/5 DRNI , 9.5c 19.2/3/5 8.6 TESI/ESP MAC Relay 8.6 B-VLAN MAC Relay PIP CBP CNP PIP CBP OR 19.2,19.3, b n DAS Intra-DAS DAS Intra-DAS Should this be a P2P BSI carrying N S- VIDs? Or, should this be a P2P B-VLAN carrying N BSIs, each with a single S- VID?

8 PBBN B-BEB B-Relay PNP B-BEB B-Relay PNP PBBN B-BEB 3. PBBN – DRNI – PBBN CBP B-Relay PNP B-BEB CBP B-Relay PNP CBP DRNI ? ? 8.6 B-VLAN MAC Relay 19.2/3/ n 19.2/3/ n 19.2/3/ n 19.2,19.3, b n 19.2/3/ n 19.2/3/ n 19.2/3/ n 8.6 B-VLAN MAC Relay 19.2/3/ b /3/ b /3/ b n n n 6.11, 9.5c 19.2/3/5 6.11, 9.5c 19.2/3/5 19.2,19.3, b n 19.2,19.3, b n PNP CBP PNP CBP OR 6.11,9.5c (BSI Relay) 19.2/3/5 6.11,9.5c (BSI Relay) 19.2/3/5 DAS Intra-DAS DRNI DAS Intra-DAS Should this be a P2P B-VLAN? Multiple CBPs have to be combined to create one Super- CBP function (instead of multiple independent CBP functions) with a single set of B-VLAN MEPs connected to the Super-CBP function at one side and multiple CBP ports at the other side. BSI UP MEPs on each CBP port can be used to terminate the Carrier MA. Super-CBP function includes a BSI Relay function interconnecting B- VLAN virtual ports and CBP ports

9 Figure drawn during Aug. 11 virtual meeting Figure was drawn to clarify interconnection of DAS function with other functions Text has been added to describe the configuration

10 DAS 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n 8.6 S-VLAN MAC Relay (EISS A) (EISS D) (EISS C) (EISS B) (EISS Y)(EISS Z)(EISS X) Figure drawn during Aug. 11 virtual meeting Text added in v01 The figures in slides 6/7 illustrate the DAS function at the boundary of the clause 8.6 S-VLAN MAC Relay (Forwarding Process) and the clause 19.2/3/5 MEP/MIP functions The figure at the right expands the figures on slides 6/7 and illustrates that the DAS function is bound by EISSs, one connected to the MAC Relay (EISS A) and three connected to CNPs or PNPs (EISS B, C, D) In general, MEP/MIP functions could be located at any EISS SAP In practice MEP/MIP functions in equipment are located at port cards (Option 1), not at switch fabric cards (Option 2) UP MEP functions should terminate Operator MA level as close to the actual E-NNI link as possible; i.e. Option 1 UP MEPs E-NNI UP MEP Option 1 Option 2 Port Card functionality Switch fabric Card functionality E-NNI Link 1 E-NNI Link 2 Intra-DAS Link E-NNI ports and E-NNI and intra-DAS ports should be on different port cards to prevent that a port card failure impacts more than one interface port. DAS function should be implemented on switch fabric card to allow that a S-VLAN can be connected to any of the E-NNI links or intra-DAS link. Frames of a S-VLAN arriving over the intra-DAS link will be forwarded to the actual E-NNI link via the switch fabric card. EISS A is a virtual EISS, not accessible for MEP/MIP functions; it is located “in the middle of a switch fabric device”. Switch fabric device has “EISS X, Y, Z, A, B and C” as I/O ports.

11 Version 01 new slides

12 Distributed version of G.8031 SNC Protection Processes 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n I-NNI Link a I-NNI Link b Distributed version of G.8031 SNC Protection Processes 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n I-NNI Link e I-NNI Link d (EISS Y)(EISS Z)(EISS X)(EISS Y)(EISS Z)(EISS X) DAS 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n 8.6 Forwarding Process (EISS A) (EISS D) (EISS C) (EISS B) DAS, c8.6 Forwarding and G.8031 SNCP Processes E-NNI UP MEPs E-NNI Link 1 E-NNI Link 2 Intra-DAS Link DAS 19.2/3/ b n 19.2/3/ b n 19.2/3/ b n 8.6 Forwarding Process (EISS A) (EISS D)(EISS C) (EISS B) E-NNI Link 4 E-NNI Link 3 (EISS N) Switch fabric Card functionality A (to be developed) distributed version of the G.8031 ETH SNC Protection processes is added, facing the carrier domain. Such distributed version of G.8031 SNC Protection processes should be implemented on the switch fabric card to allow that a S-VLAN can be connected to any of the I-NNI links. Each SNC Protection process presents the protected S-VLAN signal via the (virtual) EISS N to the c8.6 Forwarding Process. Working and Protection S-VLAN connections are connected via an I-NNI Link and the Intra-DSNCP Link. EISS A and EISS N are virtual EISSs, not accessible for MEP/MIP functions; they are located “in the middle of a switch fabric device”. Switch fabric device has “EISS X, Y, Z, A, B and C” as I/O ports. Intra-DSNCP Link I-NNI SNCP Down MEPs E-NNI PNP 802.n physical interface may be replaced by e.g. OTN interface (S- VLAN over ODUk) or MPLS-TP interface (S-VLAN over transport-LSP)

13 Example 1A – fault free condition S-VLAN k Working Gateway for S-VLAN k Typically the Active Gateway Protection Gateway for S- VLAN k Typically the Standby Gateway DSNCP process will pass through S-VLAN traffic in this mode Will become the Active Gateway if Working Gateway has failed

14 Example 1B – E-NNI Link 1 failure  DRNI protection X Move UP MEP to E-NNI Link 3 port S-VLAN k Operator MA Up MEP has been moved to E-NNI Link 3 PNP S-VLAN k connection over Intra-DAS link is now included in the operator MA Fault in DRNI does not impact protection in carrier network

15 Example 1C – I-NNI Link a failure  SNC protection X S-VLAN k Fault in carrier network does not impact DRNI

16 Example 1D – Gateway node failure  SNC & DRNI protection X S-VLAN k Working Gateway fault Operator MA Up MEP has been moved to E-NNI Link 3 PNP Protection Gateway has to become Active Gateway for S- VLAN k As Active Gateway the S- VLAN SNCP Down MEP functions are activated

17 PNP DAS 19.2/3/ b n 19.2/3/ b n 19.2/3/ b Forwarding Process (EISS A) (EISS D) (EISS C) (EISS B) DRNI in PBBN IB-BEBs E-NNI UP MEPs E-NNI Link 1 E-NNI Link 2 DAS 19.2/3/ b n 19.2/3/ b n 19.2/3/ b Forwarding Process (EISS A) (EISS D)(EISS C) (EISS B) E-NNI Link 4 E-NNI Link 3 A PBBN in a carrier domain may support DRNI as illustrated below. The two Gateway nodes are connected to a service carrying B-VLAN S and an additional Intra-DAS B-VLAN. The S-VLANs in the carrier domain are carried in B- VLAN S with an I-Tag. The I-SID of a S-VLAN may be registered at a CBP in the left Gateway, or at a CBP in the right Gateway. The S-VLANs in the Intra-DAS B-VLAN are carried with an I-Tag. E-NNI CNP PIP 19.2/3/ b /3/ b /3/ b /3/ b … 19.2/3/ b … 19.2/3/ b … (EISS Y)(EISS Z)(EISS X) PIP , 9.5c 19.2/3/5 CBP 8.6 B-VLAN MAC Relay , 9.5c 19.2/3/5 PIP 19.2/3/ b /3/ b /3/ b /3/ b … 19.2/3/ b … 19.2/3/ b … PIP , 9.5c 19.2/3/5 CBP 8.6 B-VLAN MAC Relay , 9.5c 19.2/3/5 (EISS Y)(EISS Z)(EISS X) CNP PNP Intra-DAS B-VLAN B-VLAN S Port is blocked B-VLAN Up MEPs

18 Example 2A – fault free condition … S-VLAN k ISID K is registered in this CBP ISID K

19 Example 2B – E-NNI Link 1 failure  DRNI protection … S-VLAN k X ISID K BSI K’ ISID K is registered in this CBP Operator MA Up MEP has been moved to E-NNI Link 3 PNP

20 Example 2C – I-NNI Link a failure  BVLAN S reroute …. X To recover the B-VLAN S, unblock this I-NNI port after failure of other I-NNI port S-VLAN k ISID K ISID K is registered in this CBP

21 Example 2D – Gateway node failure  BVLAN reroute & DRNI protection …. Protection Gateway has to become Active Gateway for S- VLAN k Move registration of ISID K to this port S-VLAN k X Operator MA Up MEP has been moved to E-NNI Link 3 PNP ISID K Working Gateway fault

22 PNP DAS 19.2/3/ b n 19.2/3/ b n 19.2/3/ b Forwarding Process (EISS A) (EISS D) (EISS C) (EISS B) DRNI in PBB-TEN IB-BEBs E-NNI UP MEPs E-NNI Link 1 E-NNI Link 2 DAS 19.2/3/ b n 19.2/3/ b n 19.2/3/ b Forwarding Process (EISS A) (EISS D)(EISS C) (EISS B) E-NNI Link 4 E-NNI Link 3 A PBB-TEN in a carrier domain may support DRNI as illustrated below. The two Gateway nodes are connected to multiple service carrying TESIs and an additional Intra-DAS TESI. The S-VLANs in the carrier domain are carried in a Working or Protection TESI. The S-VLANs in the TESIs are carried with an I-Tag. A Distributed version of TESI protection is to be developed. E-NNI CNP PIP 19.2/3/ b /3/ b /3/ b /3/ b … 19.2/3/ b … 19.2/3/ b … (EISS Y)(EISS Z)(EISS X) PIP , 9.5c 19.2/3/5 CBP 8.6 TESI Relay , 9.5c 19.2/3/5 PIP 19.2/3/ b /3/ b /3/ b /3/ b … 19.2/3/ b … 19.2/3/ b … PIP , 9.5c 19.2/3/5 CBP 8.6 TESIRelay , 9.5c 19.2/3/5 (EISS Y)(EISS Z)(EISS X) CNP PNP Intra-DAS TESI Protection TESI I-NNI Link a I-NNI Link b I-NNI Link e I-NNI Link d 19.2/3/ b … 19.2/3/ b … Active Working and Protection TESI MEPs Standby Working and Protection TESI MEPs Working TESI

23 Example 3A – fault free condition … S-VLAN k

24 Example 3B – E-NNI Link 1 failure  DRNI protection … S-VLAN k X Operator MA Up MEP has been moved to E-NNI Link 3 PNP

25 Example 3C – I-NNI Link a failure  TESI protection … S-VLAN k X

26 Example 3D – Gateway node failure  TESI & DRNI protection … S-VLAN k X Working Gateway fault Operator MA Up MEP has been moved to E-NNI Link 3 PNP Protection Gateway has to become Active Gateway for S- VLAN k As Active Gateway the TESI Up MEP functions are activated

27 DRNI in PBBN B-BEBs To be added in v02.