MPLS-TP Ring Protectiondraft-weingarten-mpls-tp-ring-protection

Yaacov Weingarten (NSN), Marco Corsi (Altran),

Stewart Bryant (Cisco), Bo Wu (ZTE),

Nurit Sprecher (NSN), Xuehui Dai (ZTE),

Daniele Ceccarelli (Ericsson),

Diego Caviglia (Ericsson),

Francesco Fondelli (Ericsson)

MPLS-TP Criteria for dedicated ring protection

MPLS-TP Requirements identifies five criteria for defining a special protection mechanism for a specific topology

Minimize the number of OAM entities needed to trigger the protection

Minimize the number of recovery objects needed

Minimize number of labels required

Minimize number of control and management plane transactions during a recovery operation

In presence of control plane, minimize impact of signaling and routing information exchanged

Note – no requirement has been identified to be specific to a ring topology

Status of the drafts Merged the following drafts from Hiroshima

draft-weingarten-mpls-tp-ring-protection

draft-cecarelli-mpls-tp-p2mp-ring

draft-yang-mpls-tp-ring-protection

draft-liu-mpls-tp-ring-protection

draft-dai-mpls-tp-p2mp-ring-protection

New version of draft is presented as an “applicability document” Define the problem statement –

Need to address p2p and p2mp LSPs that cross a MPLS-TP ring

Need to address both link failure and node failure in the ring

Show how we can present solutions that are dependent upon existing mechanisms without need to add any new protocols

The proposed solutions that fulfill the requirements and achieve the behavior of the criteria defined in the TP requirements

Action items from Hiroshima

Developed “applicability draft” to propose solutions based on existing MPLS survivability technologies that Optimize the parameters presented in the TP

requirements Work within the labeling mechanism of MPLS-

TP

Current draft unifies the proposals from 5 of the drafts that were previously submitted.

Next steps

Refine the text – comments are invited Work toward WG adoption