%% You should probably cite rfc8256 instead of this I-D.
@techreport{ietf-mpls-tp-temporal-hitless-psm-07,
    number =    {draft-ietf-mpls-tp-temporal-hitless-psm-07},
    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/07/},
    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 =     jul,
    day =       22,
    abstract =  {The MPLS transport profile (MPLS-TP) has been standardized to enable carrier-grade packet transport and complement converged packet network deployments. Among the most attractive features of MPLS-TP there are OAM functions, which enable network operators or service providers to provide various maintenance characteristics, such as fault location, survivability, performance monitoring and in-service/ out of service measurements. One of the most important mechanisms which is common for transport network operation is fault location. 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 effective only between end points. However, the current approach defined for MPLS-TP for the segment monitoring (SPME) has some drawbacks. This document elaborates on the problem statement for the Sub-path Maintenance Elements (SPMEs) which provides monitoring of a portion of a set of transport paths (LSPs or MS-PWs). Based on the problems, this document specifies new requirements to consider a new improved mechanism of hitless transport path segment monitoring named Enhanced Path Segment Monitoring (EPSM).},
}