Author list: Rakesh Gandhi (rgandhi@cisco) Zafar Ali (zali@cisco) - Presenter

1. RSVP-TE Extensions For Signaling GMPLS Restoration LSPdraft-gandhi-ccamp-gmpls-restoration-lsp.txt Author list: Rakesh Gandhi (rgandhi@cisco.com) Zafar Ali (zali@cisco.com) - Presenter Gabriele Maria Galimberti (ggalimbe@cisco.com) Acknowledgment: George Swallow (swallow@cisco.com) 85th IETF, CCAMP WG, Atlanta, GA (November 2012)

2. Outline • Requirements and Use Cases • Solution • Next Steps

3. Transport Requirements for Restoration LSP (1+R Use case) Working LSP OXC2 OXC1 • Resources for failed LSP need to be remain intact in at least in control plane as: • The LSP follow a nominal path (minimum latency, minimum cost, etc.). • Deterministic behavior after failure is recovered (deterministic SLAs). • Revert operation to the failed resources is desirable. • Restoration LSP is signaled after failure is detected. Restore LSP OXC3 OXC5 Ingress OXC4 GMPLS Network 15454 Egress

4. Transport Requirements for Restoration LSP (1:1+R, 1+1+R Use cases) Working LSP OXC2 OXC1 • Same Requirements as outlined in previous slide. • Restoration LSP is signaled after failure of working LSP and/ or protecting LSP. Restore LSP Protect LSP OXC3 OXC5 Ingress GMPLS Network 15454 Egress OXC4

5. Agenda • Requirements and Use Cases • Solution • Next Steps

6. PROTECTION Object with T Bit 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | Class-Num(37) | C-Type(2) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |S|P|N|O|T|Reserved | LSP Flags | Reserved | Link Flags| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |I|R| Reserved | Seg.Flags | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • Tbit – ResToration LSP • LSP Flags (Protection Types) are modified for signaling transport style restoration.

7. Solution (1+R, 1:1+R, 1+1+R) – No Resource Sharing OXC2 OXC1 OXC3 OXC5 Ingress GMPLS Network 15454 Egress OXC4 • Working LSP is signaled with: P = 0, S = 0, T = 0 • Restoration LSP for Working is signaled with P = 0, S = 0, T = 1 (after the failure of working LSP) • Protecting LSP signaled with: P = 1, S = 0, T = 0 • Restoration LSP for Protecting signaled with P = 1, S = 0, T = 1 (after the failure of protecting LSP)

8. Solution (1+R, 1:1+R, 1+1+R) – Resource Sharing OXC2 OXC1 OXC3 OXC5 Ingress GMPLS Network 15454 When red working LSP fails, it is re-signaled with S = 1 to free up resources in data plane (but still kept in control plane). Signal green restoration LSP with S = 0 to use shared data plane resources (from red working LSP). OXC4 and OXC3 share resources between red and green LSPs as S bit is 1 and 0, respectively. OXC5 and OXC4 do not share resources between green and purple LSPs as S bit is 0 in both LSPs. Once the failure is repaired, green restoration LSP is torn down, red working LSP is resignaled with S = 0 to claim resources in data plane. Egress OXC4

9. Agenda • Requirements and Use Cases • Solution • Next Steps

10. Next Steps • We would like to make this draft a WG Document.

11. Thank You.