1. Support Shared Mesh Protection in MPLS-TP IETF 83 March, 2012 Ping Pan, Rajan Rao, Biao Lu (Infinera) Andrew G. Malis (Verizon) Luyuan Fang (Cisco) Fatai Zhang, Sam Aldrin (Huawei) Fei Zhang (ZTE) Mohana Singamsetty (Tellabs)

2. Quick Background This is an important function in long-haul transport networks, as articulated in MPLS-TP (RFC5645) The design work was started a while ago The protocol and MPLS-TP packet work have been conducted in IETF The circuit network-specific (e.g. OTN) work has been conducted in ITU T15 Q9 Remarkable collaboration with all relevant parties so far IETF 832

3. Shared Mesh Protection Overview IETF 833 The resources on P-Q-R is shared by multiple working LSP’s Key properties: 1.Protecting LSP’s are pre-established 2.All protection related information has been pre-computed and download – including priority data for pre-emption 3.Upon failure, a protection LSP needs to be activated at data-plane This proposal is to specify the data- plane activation messaging sequence and format W1 W2 P1 P2

4. Complete the switch-over within one round-trip IETF 83 A BC D EFG Working LSP 4. Activation 1. Setup a protecting connection 2. Setup HW 3. Failure MPLS LabelGAL HeaderSMP commands (new channel type) (Message processing must be very efficient to achieve rapid switch-over) 4

5. Other Approach (draft-cheung-mpls-tp-mesh- protection) IETF 835 Protection Segment Protection Segment SMP messages to trigger Linear Protection Require a special LSP between a headend to a segment If a segment is shared for N users  N LSP’s Challenge: the scaling and maintenance of the control LSP’s Special LSP’s for messaging

6. Summary Shared Mesh Protection is an important function in long-haul transport networks This proposal satisfies all the protection requirements – Deterministic protection switch-over time – Scalable and simple to implement – Enable hardware enhancement for performance – Operate independent of control-plane IETF 836

7. Next Steps The proposal is fairly complete – Will enhance more in making it packet-friendly – Prototype work has been under way Requesting to make it a WG document IETF 837