1 / 9

Support Shared Mesh Protection in MPLS-TP

Support Shared Mesh Protection in MPLS-TP. IETF 83 March, 2012 Dave Allan Tae- sik Cheung Ping Pan. Contributors. Andrew Malis ( Verizon) Daniel King (Old Dog Consulting) Eric Osborne ( Cisco) Fei Zhang (ZTE ) Jeong -dong Ryoo ( ETRI) Mohana Singamsetty (Tellabs)

manton
Télécharger la présentation

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 IETF 83 March, 2012 Dave Allan Tae-sikCheung Ping Pan

  2. Contributors Andrew Malis (Verizon) Daniel King (Old Dog Consulting) Eric Osborne (Cisco) Fei Zhang (ZTE) Jeong-dong Ryoo (ETRI) Mohana Singamsetty (Tellabs) Ping Pan (Infinera) Yaacov Weingarten (NSN) Biao Lu (Infinera) Dave Allan (Ericsson) Fatai Zhang (Huawei) Gregory Mirsky (Ericsson) Luyuan Fang (Cisco) Nurit Sprecher (NSN) Rajan Rao (Infinera) Sam Aldrin (Huawei) Tae-sikCheung (ETRI) IETF 83

  3. What is Shared Meshes Protection (SMP)? Key properties: • Setup protecting LSP’s ahead of time • All protection related information are pre-computed and loaded to the relevant nodes • Upon failure, use Linear Protection mechanism in switching-over traffic • SMP protocol may be required to coordinate the usage of shared resources W1 P1 P2 W2 The resources on P-Q-R is shared by multiple working LSP’s IETF 83

  4. Background • This is an important function in long-haul transport networks • Multiple parties have been working on it for a long while • There exists several drafts: • draft-allan-spme-smp-fmwk • draft-cheung-mpls-tp-mesh-protection-05 • draft-pan-shared-mesh-protection-04 • Lack of information to chart a path forward It’s to everybody’s interest to consolidate IETF 83

  5. What we have to work with • Existing Requirements: 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. Which is a bit thin…. IETF 83

  6. The Plan • Framework and requirements • SMP Mechanisms and Procedures IETF 83

  7. Detail • Define requirements in substantially more detail • what is the problem (business priority not application priority) • preemption behavior • role of actors • what restrictions are unacceptable • Determine if protocol work is needed • If protocol work is needed, we will converge on a common solution IETF 80

  8. SMP Example ? Protection Segment Protection Segment • SMP mechanism coordinates the usage of all the shared resources on the protection LSPs • There could be multiple requests contenting on the same resources IETF 83

  9. Summary • Shared Mesh Protection is an important function in TP-enabled transport networks • Will work together on • Detailed requirements and framework • Subsequently, we will work on • State machine • Any necessary messaging protocols IETF 83

More Related