100 likes | 184 Views
draft-koike-mpls-tp-temporal-hitless-psm-01. 11 th November. 2010 Beijing Yoshinori Koike / NTT. Background. *Carrier Grade packet transport network requires MPLS-TP OAM function to be effective in maintenance operations.
E N D
draft-koike-mpls-tp-temporal-hitless-psm-01 11th November. 2010 Beijing Yoshinori Koike / NTT
Background *Carrier Grade packet transport network requires MPLS-TP OAM function to be effective in maintenance operations *If some faults or un-expected events occur, quick actions and methods are mandatory in terms of transport network requirements.
Network Objectives as transport profile • The monitoring and maintenance of current transport paths has to be conducted in service without traffic disruption. • The monitored or managed transport path condition has to be exactly the same irrespective of any configurations necessary for maintenance.
Why segment monitoring ? • Quick location of fault point & prompt handling of the problem • Segment monitoring function is mandatory in Delay Measurement and Loss Measurement • (DM and LM is supported only between MEP and MEP) • Diagnostic test and on-demand CV should be able to be conducted from an intermediate point of configured transport path.
Use cases of temporal segment monitoring Use case 1) DM and LM Packet Delay/Loss NE1(LER1) NE2(LSR1) NE3(LSR2) NE4(LER2) CE2 CE1 Transport path Segment monitoring 1 No Fault Segment monitoring 2 Detect Fault Use case 2) Diagnostic test and on-demand CV Cost effective small box (Support a subset of functions) Originator of test packets NE2(LER1) NE3(LSR2) NE4(LER2) NE1 NE5 Segment monitoring 1 Segment monitoring 2
Problem Statement regarding SPME In case of pre-configured segment monitoring (P-1) Increasing the bandwidth by the stacking shim header(s) (P-2) Increasing the identifier management of all MEPs and MIPs newly configured for SPME in the old MEG In case of temporal(on-demand) segment monitoring (P’-1) Changing the condition of the original transport path by changing the length of the MPLS frame (delay measurement and loss measurement can be sensitive) (P’-2) Disrupting client traffic over a transport path, if the SPME is temporally configured.
Potential issue of SPME • There seems significant changes in the original transport path, if SPME is set for segment monitoring. • Performing monitoring function should not change the condition of target transport path A B C D E LBL= 110 LBL= 120 LBL= 130 Before Change of Inner label value Setting SPME LBL= 100 LBL= 999 LBL= 130 After LBL= 210 LBL= 220 Change of Inner label value Change of outer label value
Conclusions • Request a new solution for temporal & hitless path segment monitoring (independently from SPME) Note: The two network objectives in page 3 and the direction for supporting the new segment monitoring were already included in section 3.8 of the MPLS-TP OAM framework-09. Note: This I-D is based on the liaison from ITU-T SG15 (LS210)
Next Steps • WG Consensus for the necessity of the new solution in MPLS-TP • Solution for temporal and hitless path segment monitoring • Creating a new solution if problems are not solved by SPME • Clarification of applicable segments in both per-node model and per-interface model • Any possible patterns between MEP-MEP,MEP-MIP, MIP-MIP including internal NE monitoring • Segment of protected transport path used for protection
Thank you Soliciting comments, feedback and suggestions for this draft from WG