1 / 11

Support Shared Mesh Protection in MPLS-TP

Support Shared Mesh Protection in MPLS-TP. March 27, 2011 Ping Pan (Infinera) Sam Aldrin (Huawei ) Luyuan Fang (Cisco). Motivation. Shared Mesh Protection is required in MPLS-TP Requirements (RFC5654) [ Req 68]: MPLS-TP SHOULD support 1:n (including 1:1) shared mesh recovery.

keelia
Download Presentation

Support Shared Mesh Protection in MPLS-TP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Support Shared Mesh Protection in MPLS-TP March 27, 2011 Ping Pan (Infinera) Sam Aldrin (Huawei) Luyuan Fang (Cisco)

  2. Motivation • Shared Mesh Protection is required in MPLS-TP Requirements (RFC5654) • [Req 68]: MPLS-TP SHOULD support 1:n (including 1:1) shared mesh recovery. • [Req 69]: MPLS-TP MUST support sharing of protection resources such that protection paths that are known not to be required concurrently can share the same resources. IETF 80

  3. Shared Mesh Protection (as specified in the Survivability Framework Section 4.7.6) • Key properties: • Protecting LSP’s are pre-established • Upon failure, a working LSP needs to activate the protection • And, it may preempt/notify other connections • If the resources are taken, it needs to try another protecting LSP (1:N) The resources on P-Q-R is shared by multiple working LSP’s IETF 80

  4. Key Design Decisions • Protection activation/preemption need to be fast and meet TP’s requirement (i.e. 50 msec) • Preferably done via hardware-assistance • Reliable messaging • The operation involves shared resources. Any message loss could cause “orphan” states inside network • Simple status queries • Optimize the protection from the head-end IETF 80

  5. Operation Example: End-to-end Activation Working LSP B C A D 1. Enable 4. Enable 2 Enable 3. Enable 5. Reply to confirm E F G Protecting LSP H K I J Working LSP IETF 80

  6. Operation Example: Preemption Working LSP B C A D 4. Send NOTIFY to alarm E F G 2. Enable 6. Enable 3. Enable 5. Enable 7. Reply to confirm H K 1. failure I J Working LSP IETF 80

  7. Operation Example: Optimize Protection through Queries Working LSP B C Get A D 2. Get 3. Get E F G Protecting LSP 5. Reply to report H K I J Working LSP IETF 80

  8. Protocol Extension • Encapsulated in MPLS-TP GAL/GACH Header • A special channel type for activation purposes • Type: ENABLE, DISABLE, GET etc. IETF 80

  9. Other Approach • “MPLS-TP Shared Mesh Protection” (draft-cheung-mpls-tp-mesh-protection-02.txt) • Developed on top of the linear protection proposal • No reliable messaging • Complex message processing (both headend and intermediate nodes can generate messages at will) IETF 80

  10. Summary • Shared Protection is required to support fast recovery in MPLS-TP • This proposal satisfies all the MPLS-TP protection requirements • Simple to implement • Cover all important aspects • Enable hardware-based implementation • Operate independent of control-plane IETF 80

  11. Next Steps • Get more feedback from vendors and providers • Make it to WG document IETF 80

More Related