%% You should probably cite rfc6669 instead of this I-D.
@techreport{ietf-mpls-tp-oam-analysis-07,
    number =    {draft-ietf-mpls-tp-oam-analysis-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-oam-analysis/07/},
    author =    {Luyuan Fang and Nurit Sprecher},
    title =     {{An Overview of the OAM Tool Set for MPLS based Transport Networks}},
    pagetotal = 21,
    year =      2011,
    month =     dec,
    day =       21,
    abstract =  {This document provides an overview of the OAM toolset for MPLS based Transport Networks. The toolset consists of a comprehensive set of fault management and performance monitoring capabilities (operating in the data-plane) which are appropriate for transport networks as required in RFC 5860 and support the network and services at different nested levels. This overview includes a brief recap of MPLS-TP OAM requirements and functions, and of generic mechanisms created in the MPLS data plane to allow the OAM packets run in-band and share their fate with data packets. The protocol definitions for each of the MPLS-TP OAM tools are defined in separate documents (RFCs or Working Group drafts) which are referenced by this document. This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunications Union Telecommunications Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the IETF MPLS and PWE3 architectures to support the capabilities and functionalities of a packet transport network as defined by the ITU-T.},
}