%% You should probably cite rfc8256 instead of this I-D. @techreport{ietf-mpls-tp-temporal-hitless-psm-08, number = {draft-ietf-mpls-tp-temporal-hitless-psm-08}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-mpls-tp-temporal-hitless-psm/08/}, author = {Alessandro D'Alessandro and Loa Andersson and Manuel Paul and Satoshi Ueno and Kaoru Arai and Yoshinori Koike}, title = {{Enhanced path segment monitoring}}, pagetotal = 16, year = 2015, month = dec, day = 2, abstract = {The MPLS transport profile (MPLS-TP) has been standardized to enable carrier-grade packet transport and to complement converged packet network deployments. The most attractive features of MPLS-TP are the OAM functions. These functions enable maintenance tools that may be exploited by network operators and service providers for fault location, survivability, performance monitoring, in-service and out- of-service measurements. One of the most important mechanisms that is common for transport network operation is fault localisation. A segment monitoring function of a transport path is effective in terms of extension of the maintenance work and indispensable, particularly when the OAM function is activated only between end points. However, the current approach defined for MPLS-TP of segment monitoring has some drawbacks. This document elaborates on the problem statement for the Sub-path Maintenance Elements (SPMEs) which provide monitoring of a segment of a set of transport paths (LSPs or MS-PWs). Based on the identified problems, this document provides considerations for the specification of new requirements to consider a new improved mechanism for hitless transport path segment monitoring to be named Enhanced Path Segment Monitoring (EPSM).}, }