draft-koike-mpls-tp-temporal- hitless-psm-02 Mar 31st, 2011 Prague Yoshinori Koike / NTT Alessandro D'Alessandro/ Telecom Italia

Updates Mr. Alessandro D‘Alessandro of Telecom Italia joined as a co-author. Reflected comments from mailing-list discussion Aligned the network objectives with the descriptions in 3.8 of mpls-tp-oam-framework Added an example of Sub-path Maintenance Element (SPME) to clarify the necessity of the enhanced in-service segment monitoring Added requirements for enhanced in-service segment monitoring

(1) On-demand hitless segment monitoring at least in single layer Segment Layer 1 Transport path (MEP-MEP) A Segment Layer 2 Segment Layer 3 BCDE On-demand and in-service “single-layer” hitless segment monitoring is mandatory. It provides a method for a defect localization On-demand and in-service “multi-layer” hitless segment monitoring is optional. Multi-layer measurements in parallel achieve a strict and efficient defect localization by using the results of the same time flame. Multi-layer monitoring

(2) On-demand segment monitoring independent from proactive monitoring of ME Segment Layer 1 Transport Path (MEP-MEP) ABCDE Proactive monitoring of original transport path On-demand in-service segment monitoring Must be independent “On-demand and in-service” segment monitoring should be supported without disabling the pro-active monitoring of an original transport path. Note: Bandwidth design for OAM packets used by the on-demand and in- service segment monitoring is operators’ design issue.

(3) Diagnostic procedures for defect localization On-demand and in-service segment monitoring should be supported in an arbitrary segment of a transport path. ABCDE Segment monitoring Flexible segment monitoring : proposed Constrained segment monitoring :not reasnable Constraining one end point of on-demand segment monitoring is not desirable because it limits deployment scenarios Transport Path (MEP-MEP) On-demand segment monitoring in any segment

Summary of additional requirements On-demand and in-service “single-layer” segment monitoring is proposed. Multi-layer segment monitoring is optional. “On-demand and in-service” single layer segment should be done independently from pro-active monitoring of an original ME of a transport path. On-demand and in-service segment monitoring should be able to be set in an arbitrary segment of a transport path.

Next Steps Solicit feedbacks on the draft, particularly from operators Update the drafts based on the comments  Reflect comments from Deutsche Telekom  Mr. Manuel Paul joins as a co-editor Request to make this a WG draft

Thank you