1. Geneva, 28 May 2010 PBB-TE Infrastructure Protection Switching Operation Bob Sultan, Huawei Technologies Joint ITU-T/IEEE Workshop on The Future of Ethernet Transport (Geneva, 28 May 2010)

2. Geneva, 28 May 2010 2 Topics Review PBB-TE Forwarding The Infrastructure Segment and IPG Monitoring the Segment Provisioning an IPG Infrastructure Protection Switching

3. Geneva, 28 May 2010 3 Ethernet Switched Path (ESP) forwarding is based on provisioned 2-tuple and associated outbound local port; PBB-TE Forwarding (ESP) D C B A E Port Out P2 P1 P3 P2 P1 P2 P3P1 P3 P2 Port Out P3 Port Out P1 Filtering Database (FDB) B FDB D FDB C ESP X

4. Geneva, 28 May 2010 4 A pair of counterdirectional congruent PtP ESPs form a PtP Traffic Engineered Service Instance (TESI); IPS also applies to linear portions of PtMP TESIs; PBB-TE Forwarding (TESI) D C B A E Port Out P2 P1 P3 P2 P1 P2 P3P1 P3 P2 Port Out P3 Port Out P1 Filtering Database (FDB) B FDB D FDB C P2 P1 P1 ESP x ESP y TESI

5. Geneva, 28 May 2010 5 A segment is specified by a sequence of ports: Green: B.P2 – C.P1 – C.P3 – D.P2 Red: F.P2 – G.P1 – G.P2 – H.P2 Bridge terminating a segment contains exactly one port associated with that segment; Segment D C B A E P1 P3 P2 P1 P2 P3P1 P3 P2 ESP x H G F P1 P2 P1 P2 P1

6. Geneva, 28 May 2010 6 The state of an Infrastructure Segment is monitored by a Maintenance Association (MA) specific to that Segment; Distinct type of MA; not the same as the PBB-TE MA associated with a TESI; Terminates at PBP vs. CBP; Down MEPs vs. Up MEPs; Segment Monitoring D C B A E Green MEP Green Segment MA CCM

7. J Geneva, 28 May 2010 7 Non-overlapping segments having the same pair of segment endpoint bridges (SEB) form an IPG; A Bridge maintains a table for each IPG terminating in that Bridge (just one shown in this figure); The table contains a list of 2-tuples representing traffic provisioned to follow one of the Infrastructure Segments which is known as the Working Segment; Infrastructure Protection Group (IPG) D C B A E H G F SEB I IPG Working Segment

8. J Geneva, 28 May 2010 8 The Protection Segment provides an alternate path for traffic associated with the listed 2-tuples for the IPG; The IPG maintains the local port numbers associated with the Working and Protection Segments respectively; Protection Segment D C B A E H G F SEB I IPG Working Segment Protection Segment P3 P2 P3 WS: P2 PS: P3 IPG WS: P2 PS: P3

9. Protection Segment Provisioning J Geneva, 28 May 2010 9 Same list of 2-tuples at F, G, H; but provisioned as if traffic was forwarded on Protection Segment; D C B A E H G F I P3 P2 P3 Port Out P2 FDB B P1 P2 P4 P1 P4 Port Out P2 FDB F P1 P2 P1 P2 IPG WS: P2 PS: P3 IPG WS: P2 PS: P3

10. Infrastructure Protection Switching J Geneva, 28 May 2010 10 Protection switch triggered by detection of state change in IPG Segment or manually; Requires FDB update only at endpoint bridges; Update only entries with 2-tuple in IPG list; D C B A E H G F I IPG P3 P2 P3 WS: P2 PS: P3 IPG WS: P2 PS: P3 Port Out P2 FDB B P1 P2 P4 P1 P4 P1 P2 X Port Out P1 FDB D P2 P4 P2 P3 P1 P4 P3

11. Further Points Geneva, 28 May 2010 11 The IPS State Machine is identical to the TESI Protection State Machine Except for the lowest-level functions that update the FDB outbound port values instead of changing the mapping from backbone service instance to BVID; The TESI Protection State Machine is similar, but not identical, to the G.8031 State Machine; IPS specifies optional M:1 protection, deployed by using an alternate Protection Segment when a Protection of higher priority is not available; IPS supports the nesting of IPGs but this requires appropriate provisioning of hold-off timer values; Further, the MA associated with the outer IPG must be provisioned to be protection switched by the inner IPG when a failure of the inner IPG occurs;

12. Thank You Geneva, 28 May 2010 12